Hi all,

I talked to my colleagues. They and I are happy with the recently provided solution. But we all would prefer the rich Jira plugin solution in the long term!

Thanks again guys for your work!

Cheers

Hey Pablo, hey Daniel,

sorry for the delay. We had a critical stage in our project lately.

Thank you very much for the improved extension!

I have some further ideas:
- availability to have more than one Project key: In our company we are using several Jira projects based on the same PlasticSCM repository, therefore it would be nice to have the possibility to link it with the other Jira projects
- I would really appreciate a rich Jira plugin, like the one for Stash or FishEye: Issue screen - Activity - Source Tab -> all relevant PlasticSCM infos about Changeset, commits, comments,...

I will talk to my colleagues to come up with some more ideas.

Thanks again!

Cheers,
Michael

Hello everyone,

We need your feedback in order to be able to move forward with this task.

Daniel (one of the Plastic SCM senior developers) asked a few questions last 21st and also submitted a blog post with details about the new JIRA implementation we've created.

We do really need your feedback in order to move forward.

Otherwise we consider the new implementation submitted by Daniel is enough to get the task closed.

Thanks!

pablo

Plastic SCM staff - http://www.plasticscm.com/company/team.aspx

We have improved our Jira extension. It also works with JIRA 6. Now you can:

* View the changeset changes in the WebUI or in the PlasticSCM client from the Jira task.
* Customize the data and the format that are logged to the custom field.

More details: http://codicesoftware.blogspot.com/2014/03/jira-6-integration-improvement.html

What any other feature you would like to have here?

We would like to implement a rich Jira/FishEye plugin, but the problem is that right now that API is closed. We cannot develop a rich FishEye integration at this moment. We are trying to talk to Attlassian people.

that's an good idea! I would prefer a plugin like the svn one (https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugin.ext.subversion). I mean plasticscm costs several thousand bucks for a decent development team, so a perfect integration to highly common tools like jira will be expected!!

You are right, this custom filed makes it very confusing if you have more than one changeset per feature branch, as usual. I am missing a plugin too. We recently update jira to the newest version and the old plastic plugin isnt available any more :-(

Would be great to have such a feature as in our company we were used to a similar one when using subversion.

yeah man, that's exactly what we are looking for!!!