The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 

Jira Automation - Transition a ticket to Backlog if the Sprint is set to unassigned.

Requirement

Using Jira Workflow validation I have configured this: "A ticket can  be transitioned from Backlog to To Do only if it is assigned to a Sprint." This validation restricts user to migrate a ticket from Backlog to To Do.

Now when the sprint value is removed from a sprint, the ticket should also be automatically transitioned to Backlog.

 

I've accomplished this using Jira Automation. Snapshot below is the automation that displays how this is achieved.

Screenshot from 2023-09-06 14-34-50.png

I ran few searches if there were a simple way to do this without using the automation rule. I failed! I would appreciate if the community could help in achieving this from other Jira inbuilt features.

Thanks

4 comments

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

Andrew Culver
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 6, 2023

An automation rule is the correct way to accomplish this.

Like • Sanjog Sigdel likes this
Tomislav Tobijas
Community Champion
September 6, 2023

I agree with @Andrew Culver - I would probably immediately go for automation on this. Is there any particular need why you wouldn't do it with automation?

Like • Sanjog Sigdel likes this
Sanjog Sigdel
Community Champion
September 7, 2023

@Andrew Culver Thank you for the feedback.

@Tomislav Tobijas My first choice is also Automation. But with my Jira Standard Plan, I can only execute 500 automation rules per month. I maange 7 projects in Jira. Two Sprints for seven teams with say, an average of 10 tickets, occupies 140 rule execution. As I have other automation rules running, I was curious if this could be handled from Post Functions only.

Thank You

Like • Tomislav Tobijas likes this
Tomislav Tobijas
Community Champion
September 9, 2023

@Sanjog SigdelI was digging around and I also couldn't find any solution without using A4J. As a start reference, I was thinking of using webhooks (Settings > System > WebHooks) but this part only covers sending information about the change/issue (sprint) update. Then I looked at workflow triggers (in native Jira) these only cover events received from other applications (e.g., Bitbucket or GitHub).

I guess you could take a look at some marketplace apps that would extend triggers with some additional events or you could get more into Forge to try to build the app yourself (basic example) that would get you to that desired result. I'm not that much into forge so I can't be much of assistance here 🫤

Like • Sanjog Sigdel likes this

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

TAGS
AUG Leaders

Atlassian Community Events