Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,277
Community Members
 
Community Events
176
Community Groups

Changing issue type when a workflow transition occurs

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.

5 answers

1 accepted

0 votes
Answer accepted

>> 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.

Hi Sheila,

As far as I know, you can't. Link to one of related questions with answer:

https://answers.atlassian.com/questions/220469/change-issue-type-automatically-on-transition

Regards,
FLorjan

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.

You can absolutely do this within JIRA using Automation

Follow these steps:

> Click Project Settings in the left-hand navigation panel

> Click Automation (third option from the top)

> Click Create Rule in the top right corner

> Use the "Issue Transitioned" Trigger

> Select your "From" and "To" statuses

> Click Save

> Click New Action under the Add Component area

> Choose Edit issue in the Recommended list of actions.

> Choose Issue Type in the list of fields to edit

> Choose the issue type to which it should transition

> Click Save

> Name your Automation

> Click Turn it On

> ALL DONE!

Screen Shot 2021-02-10 at 2.44.38 PM.png

0 votes

I have a scripted function I use to move issue types to different workflows. It is certainly possible to script this out using script runner.

Our use case is a triage process in one of our service desk projects that depending on team selection it sends the issue to one of 5 different workflows/issue types.

 

Regards,

Steven

@Steven Mustari 

Can you provide the script you used?  

Thanks!

Stacy

I might've been too quick to the draw on my answer here. The script I have is for DC/Server and not in Cloud. I would need to spend some time to see if this is possible through to API to do.

Apologies for my original short sighted answer to this one!

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?

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.

Hi,

I saw in marketplace that this add-on is not available for Cloud. Is this information right?

Regards,
Florjan

Sorry, it is not available for Cloud (OnDemand) at this time. Vote and watch CW-18.

Like Josh Hemond likes this

Suggest an answer

Log in or Sign up to answer