Hi - I'm in cloud. I added an new issue type called 'wishlist' and a new status 'proposed'. And created a new workflow around it such that when a new issue is created with issue type = wishlist, the status is 'Proposed'. When someone Approves it (transition), the status becomes 'planned' and follows the regular jira defaul workflow. All other issue types follow the default jira workflow. I wanted to know if it's possible that one someone approves an Wishlist issue that the issue type can automatically change from Wishlist to User Story. Is there a way to do that? I searched and couldnt but I'm wondering if I missed something.
>> I wanted to know if it's possible that one someone approves an Wishlist issue that the issue type can automatically change from Wishlist to User Story.
As far as I know, you can't. Link to one of related questions with answer:
I suggest that you have only one issue type (e.g. User Story) and another custom field with two values (e.g. Wishlist and Approved Request).
With such approach you will be able to move to different statuses on transition based on value in new custom field. You will be also able to change value of this custom field on transition.
To have more post-functions on workflow transitions you need to enable JIRA Suite Utilities and JIRA Misc Workflow Extensions plugins on your ondemand instrance.
Update issues post function from Update on Transition for JIRA can change the issue type and other things. The point of the referenced answer is that you need to be careful, however in many standard use cases it is fine. In other cases, you may need to provide or update other fields. Test your use cases to make sure it behaves as expected.
I have the same need, but we use server, can anyone please recommend on the addon/way to do it?
Basically the request is such:
We are creating the issues automatically via Scumblr (automated crawler) and the issue created of type A.
There's a specific group of users that need that this issue would have special fields, that relevant only for them, so I've created another issue type with all those fields. Those fields are irrelevant for other users in other projects which all are using type issue of type A. So, I thought of finding a path to convert upon creation all issues from type A to type B.
Is there more elegant solution that I didn't think of?
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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