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

Automation trigger on release start date

Fong Xu

Hi,

I am creating an automation rule in Jira automation section. but i am not sure how to create a trigger on Release dates, such as start date. I know that when you enter a fix version on a jira card, the release date is defined by default. So I think I can use the release start date to trigger an rule. Any suggestions?

Thanks,

Fong

Accepted answers

All comments

Robert Wen_Cprime_

Hello @Fong Xu ! Welcome to the Atlassian Community!

This previous question talks about the same thing with regard to Release Date: https://community.atlassian.com/t5/Jira-Software-questions/How-can-I-use-the-release-date-of-a-version-in-JQL/qaq-p/1753211

I found the same thing where I couldn't use Release Date as a trigger or condition in Automation.

Bill Sheboy

Hi @Fong Xu -- Welcome to the Atlassian Community!

Would you please describe the problem you are trying to solve? Knowing that may help the community to make suggestions.

Until we know that...

Let's assume you want to do something with issues assigned to a release. In this case, you could gather the issues (with another trigger, branch, or lookup issues), and then parse out the release's information to take action.

Or, perhaps you want to do something based on releases which are not yet assigned to issues. You could use a daily scheduled trigger, call the REST API to access the versions for the project, and then take actions based on the version information.

Both of these are more complicated rules and so knowing what you are trying to accomplish would help.

Kind regards,
Bill

Fong Xu

Hi Bill,

Thank you for the info!

I look for a way to create a jira card/issue automatically every time when a release start or release date is defined.

When we assign a card or more than one card to a release, we use the fix/version field. by doing this, a release will be created in jira in Jira Releases section. I think I misspoken, the release date is not defined by default. When we confirmed a release, we will enter the release date, at that time, I hope that the automation that I need will automatically create a Jira card that lists generic implementation plan in the description field, so that we then assign the card to a developer who can use it during the actual release. I am able to create an automation, (I think Jira calls it Rule), that can create a card with the implementation plan that I defined when a fix/version field is entered. But this triggers to create a card every time that issue field updates…

Any ideas that I can fix it?

Thanks,
Fong

Fong Xu

Hi Thanks for your info!

So it is not possible to use Release Date as a trigger or condition in Automation?

Are they going to enhance it, so that this feature could be available in the next version of Jira?

Thanks!

Bill Sheboy

Thanks for that information. First thing, I recommend mapping out all of your scenarios as this will help determine what is (or is not) possible with automation for Jira rules.

With that noted, there are two triggers that you might use if you flip the way you think of the scenarios...What if you detect when the version is created/updated to create the issue instead of when the dates arrive?

Version Created trigger: when a version is created, you could check for the information such as Start Date, and create the new issue. Then if needed, use a scheduled trigger to act on that new issue.

And for the case when the dates were not set when the version was created, you could use the Version Updated trigger, check if the dates were set, and then create the issues as before.

Fong Xu

Thank you for the suggestion.

Do you mean that we can continue to use the fix/version field in an issue to create a Release item. Then when a release is confirmed, we will update the release item’s start date or release date in the release item, we can use version update trigger instead of issue update trigger, right?

Let me check how to use version update/creation as a trigger instead of issue fix/version update/creation as a trigger. i will keep you posted.

Thanks!

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software