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
Community Members
Community Events
Community Groups

New tickets automatically get moved to the current sprint

We use to automatically create Jira tickets from the functional account.

This is functional however we are looking to have new tickets automatically get moved to the current sprint of the XYZ board.

Thanks in advance.


2 answers

2 accepted

0 votes
Answer accepted

Hi @Rajesh Shetty -- Welcome to the Atlassian Community!

What problem are you trying to solve by doing this? 

As Nic notes, automatically adding work to an in-progress sprint will have unintended consequences...such as reducing your team's confidence/predictability of sprint planning to deliver value.

Kind regards,

0 votes
Answer accepted

Welcome to the Atlassian Community!

Doing this destroys the usefulness of Scrum, so it is a really terrible idea.  It's the antithesis of what Scrum does, it renders your planning utterly pointless, breaks all your Scrum reporting, and stops you from ever being able to improve.

If you genuinely are working in a way that takes new work into a sprint automatically, without planning, then I'd very strongly recommend that you stop pretending you're an Agile team, and move to either a Service Desk project or a Kanban board, where you do "drink from the firehose".

That said, yes, you can break your Scrum with Automation.  Set up an automation that triggers on "issue created" and edits the current issue, setting the sprint field to something (you've got a number of options there, I don't need to explain them here, the drop-down is clear!)

Hi Nic,
Indeed..! I accept you suggestion and consequences if we do that.
Fortunately I has to do it, as it a customer requirement.

Please suggest if you have solution for Automation rule.

Thanks in advance.

I'm afraid you need to go back to your customer and tell them their "requirement" is, well, to be diplomatic "non functional".  It's simply going to break everything and they should not do it.

Tell them that the better options are to stop doing sprints and adopt a queue-like system.  Scrum is not right for them, obviously.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Atlassian Automation

Jira Automation: Sum Up Story Points Roundup (Initiatives -> Epics -> Story/Tasks -> Subtasks)

Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...

3,108 views 10 9
Read article

Atlassian Community Events