Trying to create a JIRA workflow and in looking around it seems that most companies (ones I could view issues) seem to have the resolution step after the coding piece (In Progress) was completed. Our company has coding, code review, testing, and now we're implementing test review stops in a workflow. We're evaluating JIRA, Fisheye/Crucible and Confluence and I was wondering why having the resolution step after coding seems to be the most preferred set up and how it works with Releasing Versions?
It is neither a prefered workflow configuration nor a recommended approach. I guess people just likes it simple. It such cases, they release the code as soon as someone worked on it - even if they are doing some testing in the background.
It is perfectly okay to have the review, testing steps in the workflow and set resolution after that. I have seen quite a lot of companies doing that.
As Jobin mentioned, there really isn't a preferred workflow configuration, as it all depends on how you would like to track the current status of your project/issue. You can include as many status-es and workflow transition as you require.
Now, as for viewing the workflows of other companies, this can be a bit tricky. One method that I did discover is by importing their workflows. Please note that this is only available from JIRA 6, but if you are currently on that version, then you should be able to Import Workflows.
Provided that the companies have uploaded their workflow to the Atlassian Marketplace, you would be able to import them and use/analyze them in your own instance
We're looking for participants for another workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sh...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG