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; } } }

Increment data number on summary field when a new ticket created from Jira Automation on Schedule.

Rajesh Konda

Hi All,

I have a requirement to auto create tickets on scheduled basis with jira automation, and on summary field each time a ticket is created it should increase number ex

1. schedule

Summary : XXXXXXXX Release 21

2. Schedule

Summary : XXXXXXXXXXX Release 22

3. Schedule

Summary : XXXXXXXXXXX Release 23

each time a new ticket created the release number should increase, can any one suggest how can i achieve. Thanks

Regards,

Rajesh

Accepted answers

Bill Sheboy

Hi @Rajesh Konda

I can think of three ways to accomplish this:

Use the Lookup Issues action with JQL (e.g. project = myProject AND summary ~ "Release" ORDER BY summary DESC) to get the last issue created, and then extract and increment the value
Use a project entity property to store the last value used, and increment it as needed
If you are using versions (releases) to support this approach, find the last released version (or upcoming one) to extract the number and increment it

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Rajesh Konda

I can think of three ways to accomplish this:

Use the Lookup Issues action with JQL (e.g. project = myProject AND summary ~ "Release" ORDER BY summary DESC) to get the last issue created, and then extract and increment the value
Use a project entity property to store the last value used, and increment it as needed
If you are using versions (releases) to support this approach, find the last released version (or upcoming one) to extract the number and increment it

Kind regards,
Bill

Rajesh Konda

Hi @Bill Sheboy Thank you for response, unable to understand from where to start. Can you please suggest with an example please.

Regards,

Rajesh.

Bill Sheboy

Hi, Rajesh. I will try to help with more details, but first...

Are you using Jira versions along with this or are these "Release" values independent of the built-in ones?

You note doing this on a schedule. What drives that schedule? Some event happening or is this just on time, such as every 3-days?

Thanks!

Rajesh Konda

Hi @Bill Sheboy

We are not using version, actually these versions are from developers project and they want an automation to be created on db project with their release. DB team is not using the versions or release on their one.

Yes the automation is schedule and it executes every 3 weeks.

Abhi_p6ixe9

Hello @Bill Sheboy

Can you please Suggest me the automation Rule for Below example:

I have seeking your help because this seems to be close to my example below:

To have a field that is automatically populated on creation, with the value "REQ.(N+1) where N is the value from the most recently created story., and whenever a issue type = story is deleted, Then it has to continue the Next Incremental value , when a new story issue is created.

Please let me know if any information is in need from my end.

Regards,

Abhi

Bill Sheboy

Hi @Abhi

I suggest you create a new question, and link back to this thread. Otherwise only the people following this one will see it.

When you do that, please post images of your complete rule, the audit log details showing the rule execution, and describe what is not working as you expect. That will provide context for the community to offer suggestions.

Kind regards,
Bill

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

jira-software-cloud