Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

If all issues are done for that release & release date is passed,can we mark Fix Version as released

Can we develop Jira automation rule which checks if all issues are done for that release & release date is passed. If both conditions are met, fix version should be marked as released.

Actually I have developed the rule but it does not consider all the issues. It checks one at a time like status is done and release date is passed, it will mark that fix version as released but that fix version is having other issues which are not in done status.

Can refer the below snap.

fixVersion.png

1 answer

Hi @Mohini Chandwani 

To do what you ask, you could use Lookup Issues actions and JQL to check the count of issues in particular conditions, and then release the version when satisfied.  For example:

  • Trigger: scheduled (no JQL needed)
  • Action: lookup issues on JQL for fixversion = earliestUnreleasedVersion()  ...which gets all issues in the next release
  • Condition: check the version date of the first issue in the lookup is past (or today if you want)  {{lookupIssues.first.fixVersion.releaseDate}}
  • Action: lookup issues on JQL for fixversion = earliestUnreleasedVersion() AND status NOT IN (Closed, Done) ...or whatever your final status values are
  • Condition: check the count is zero  {{lookupIssues.size}}  ...to confirm no open issues remain for the release
  • Action: Release version ...which should release the earliest unreleased version

Best regards,

Bill

Hello @Bill Sheboy ,

I am using Server version so lookup issue component is not available.

And for trigger part using scheduled but it requires JQL because if I choose simply run the conditions and actions without providing issues option it gives the following error.

scheduled.png

Is there any way using webhook data or any other approach to do this?

Hi @Mohini Chandwani 

Sorry, I did not catch that you were on the server version when I answered.

Yes, you could use a web request such as to call the REST API for some JQL to replace what lookup issues could provide.  Here is an article on using that technique:

https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

As another alternative, you could also use a branch to update some indicator entity properties in the version.  Then check those to decide if the version should be released.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Automation

Announcing the Jira automation template library!

Hi all,  After many months of work, I am delighted to announce the launch of the Jira Automation Template Library!  The Template Library is a new website dedicated to all things Jira au...

965 views 17 24
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you