This is a re-post of a question at S.O.
Our JIRA workflow for development issues goes something like this:
New -> In-Progress -> Resolved -!-> Reviewed -> Closed/Released
This is simplified, but should get the point across.
The Jira Assignee for New/In-Progress is simple: It may start out being assigned to anyone, but as soon as it's in-progress the developer that codifies the issues is the Assignee.
When the developer is done he will check-in and set the issue to
Now my "problem"(*) starts: Since the developer should not review the issue himself, the issue should be assigned to someone else for review. The reviewer can then approve it and set it to
Reviewed, after which it is ready to be included in a release. (details on how that works not relevant here)
The issue then ends up with the Assignee set to the reviewer, where the relevant person for the issue is actually the original developer.
I mean: When looking at Jira issues, I'm mostly interested in the Implementer, not the person that approved the change afterwards.
So the question(s) seems to be:
I guess one could add additional fields, but the fact that the defaults only have these two People should hint at something?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs