Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
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

Synchronizing sister issues

Hi all, 

I have 2 stories S1 and S2 of 2 distinct story types Each has its own statuses and its own workflow because each has its own process. however, S1 and S2 are linked to the same epic (same parent). 

I need to implement a synchronisation between S1 and 2 because, a status transition on S1 is condition for a transition on S2. The sole common thing between both stories is their link to the same parent. My current problem problem is to synch sister issues. If S1 does not exist, S2 has no sister and processing S2 does not rely on any other story. 

I have read so far conditions can be for all child subtasks for an issue but nothing about sister issues. I explored creating a single workflow combining S1 and S2. But there again, S1 can have a life of its own. Same thing for S2. But if both exist with the same parent, synch is needed.

Any help is warmly welcomed. Thanks.

2 answers

2 accepted

Hi,

If you have JMWE, you can do it using the "Transition Related Issues" post-function. 

  1. Add the post-function to the workflow of S1
  2. Input the transition to be triggered on S2
  3. Select "Issues returned by the following JQL search" under "Target issues"
  4. Input a JQL that results in S2. Say, Epic link = "Scheme" and issuetype = "S2 type"
  5. Save the post-function
  6. Publish the workflow
  7. Repeat the same for all other synchronizations.

Regards,

Radhika

0 votes
Answer accepted
John Funk Community Leader Jun 01, 2020

Hi @Jean-François RIOU ,

Do you have Automation For Jira or ScriptRunner? It could probably be done with one of those, but I do not use ScirptRunner so I could not offer any advice there. 

John Funk Community Leader Jun 13, 2020

Glad you were able to get up and running.  :-)

Like Jean-François RIOU likes this

Suggest an answer

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

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

322 views 9 7
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