Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

When all of one issue type in epic reach status, update epic (using multiple issue types in status)

Hi!

I've searched the community questions for this, but the only thing that came close was this

So I'm trying to have an epic update when all issue of type 1 reach a status, and issue type 2 can be ignored.

In the epic 2 types are living, stories and tasks

I tried the following:
- Have automation listen to the correct statussese (Alpha fixes or Beta revision)

- For Epic, if stories (or other issues in this epic) match JQL: issuetype = Story AND status = "Alpha fixes"

- Then Transition issue (epic) to 'copy from trigger issue'

 

This fails on me... any suggestions?

1 answer

1 accepted

Here's the overview of the automation, I tried to make it work for apha fixes first, before I add beta revisions to this automation :)

In below example, I would have expected when I updated story 2 to Beta revisions, the epic to be updated to this status too (which it didn't)

image.png

image.png

 

So above does not work... any reason?

frother Atlassian Team Mar 03, 2021

Hi Bart, 

I believe this is failing because not all issues in the epic are of type "Story", you have some tasks in there also.

Instead of checking "stories in epic" in your related issues condition, use JQL instead like this:

"Epic link" = "{{issue}}" AND issuetype = "Story"

Then all match jql

status = "Beta revisions"

Hope that works.

Scott.

This is amazing.... I would NEVER have come up with this, many thanks!!!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

New Cloud Apps Roundup - Spring 2021

Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...

221 views 3 20
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