There are a bunch of Bugs that were closed by team without having a resolution. My objective is to create a bulk change for all these tickets which is in Dev Complete status but have Resolution as Unresolved.
In order to do this, I am trying to add a transition from say Dev Complete to Dev Complete, I wasn't able to see the post function. Was I supposed to see the Post Functions and able to add a Resolution as say Resolved? Note: I tried to click on the transition but it won't let me click on a transition.
I was hoping that I could do this and get a filter to do a bulk change based on above created transition. Any idea what am I doing wrong here?
Hello @Avinash A P
Welcome to the Atlassian community.
I agree with @Scott Schellhardt that it is atypical to set the Resolution field when the issue has not yet reached its final status.
In what type of project is this workflow used? Is it a Company Managed project or a Team Managed project?
Team Managed Project:
In a Team Managed project you don't have direct access to set the Resolution field during a transition. The Resolution field will be set to Done when an issue transitions to a status that is color coded green. Your Dev Complete status is blue.
Every status is assigned to a Status Category. Each Status Category has an associated color.
To Do - gray
In Progress - blue
Done - green
If this is for a Team Managed project the Resolution field can't be set during the transition when the destination status is in the In Progress/blue category. You would have to change the Status to being in the Done/green category.
Company Managed project:
If this is a workflow in a Company Managed project then you need to:
Click the + next to Rules on the right.
Select Perform Action / Update an issue field
Select the Resolution field and specify a value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Given that it is a Team Managed project, as I said you will not be able to set the Resolution field directly.
The Resolution field will be set automatically when issues transition to a green color-coded status. It will be cleared automatically when they transition to a status that is blue or gray. If you want the resolution set for the specified status, which is currently blue/In Progress, then you will have to change its Status Category to green/Done.
Additionally there is only one Resolution value available in Team Managed projects, and that is "Done". There is a change request to enable customization allowing different values to be specified.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Avinash,
For the first part of your question, you shouldnt need to put a transition from Dev Complete to Dev Complete. You should be able to just add a post function to the In progress>Dev complete to Set Resolution. I would also add one to Clear resolution on the rework transition to remove the resolution that gets set when you transition to Dev Complete.
I do find it a bit odd that you are looking to set a resolution before the ticket flow is completed, but to each their own.
For the bulk change piece, I would take a look at this article if you havent already:
https://confluence.atlassian.com/jirakb/bulk-update-the-resolution-field-in-jira-321857142.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Scott for your feedback. It was setup in a way like how you explained, it was me who was looking to edit the flows thinking we will need to have resolution when Dev Fix is provided but then I see your point where the resolution could be changed again if the fix doesn't work, so it makes sense to have the resolution at the end of the flow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.