nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automating Ticket Creation in Future Sprints

Tyden Ruud

Hello!

I was wondering if it's possible to automate the creation of a set of tickets that gets added to each new sprint at creation regardless of order. It seems the sprint field on ticket creation is limited to active or next sprint. But for my use case, the sprint could be any number of positions in the project. So I'm not too sure how to define that I want my tickets to be created in any sprint that gets created.

Thank you,

Tyden

Accepted answers

Trudy P Claspill

Hello @Tyden Ruud

Brainstorming here... I haven't tested this out.

Do you have a rule that creates the issues? Consider setting the trigger of that rule to be an Incoming Webhook.

Create another rule that is triggered by Sprint Created.

In that rule use the Send Web Request action to call the issue-creating rule. Send the newly created Sprint's ID as part of the payload to the issue-creating rule.

In the issue-creating rule, get the Sprint ID from the payload and use that to set the Sprint field of the newly created issues.

I'll have some time later to try to work out those details in testing, but I wanted to provide at least the idea in case you want to work on it yourself.

All comments

Trudy P Claspill

Hello @Tyden Ruud

Brainstorming here... I haven't tested this out.

Do you have a rule that creates the issues? Consider setting the trigger of that rule to be an Incoming Webhook.

Create another rule that is triggered by Sprint Created.

In that rule use the Send Web Request action to call the issue-creating rule. Send the newly created Sprint's ID as part of the payload to the issue-creating rule.

In the issue-creating rule, get the Sprint ID from the payload and use that to set the Sprint field of the newly created issues.

I'll have some time later to try to work out those details in testing, but I wanted to provide at least the idea in case you want to work on it yourself.

Tyden Ruud

That's an interesting thought- I will see what I can come up with using that method. Thanks for brainstorming!

Jeffrey_Denton

Hi Please share your automation and audit log.

Bill Sheboy

Hi @Tyden Ruud

Adding to Trudy's suggestions...

With the Sprint Created trigger, the {{sprint}} smart value is provided: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/#--sprint--

And so the rule could directly enter the ID when the story is created as {{sprint.id}}

Many fields in the Create Issue action provide dropdown values, such as for Sprint. It is not always obvious from the UX that a smart value may be entered. To do so:

type in (or copy-and-paste) the smart value
when it appears below the field, select it for use

Kind regards,
Bill

Tyden Ruud

Thanks Bill!

That set me on the right track, putting the smart value {{sprint.id}} into the sprint field on a ticket create action did the trick! Thanks for pointing out that smart values could be used, the UX makes it seem limited to copying or setting the next or active sprint options! Made the operation much simpler than a lot of other routes I was taking.

Thanks again,

Tyden

goekce.vardar1

Hey @Tyden Ruud

I'm also struggling with the same issue.

Could you maybe share your automation here?

Thank you!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud