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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,455,845
Community Members
 
Community Events
176
Community Groups

Automation - If linked issue type is... then do this.. else..

Hello Team! 

I have a question regarding JIRA Automation. 

I want to, depending on the linked issue type, answer Yes or No on a Custom Field in my project. Does anyone see a solution for this? 

Thank you!

1 answer

0 votes
Stefan Salzl Community Leader Jul 12, 2022

Hi @Johannes Nyberg ,

an automation rule needs an event. When should the rule be triggered?

How far did you come so far? Could you please share a screenshot of what you tried so far?

Best
Stefan

Hi Stefan, 

Sorry for my undetailed question. 

 Yes, so it should be triggered when an linked issue is created. I have the following setup:

- Project A and issue type X

- Project B and Issue type Y & Z

The support team ( works in project B ) will create a linked issue in project A with issue type X. The created issue in project A will either have Y or Z as a linked Issue Type. 

Depending on that linked issue type I want to edit the created issue in project A. 

This is my progress

Capture.PNG

Any suggestions @Stefan Salzl ? 
Thank you, 

Johannes 

Like Stefan Salzl likes this

Hi @Johannes Nyberg 

thanks for the reminder and your patience ;)

according to your description: I was thinking of another trigger -->

  • "issue linked"
    • You could then also choose on which link type the rule should react/be triggered.
    • It also depends on the direction/type your linking is going (inward/outward linking --> which issue will be the inward-side and which one the outward-side)
  • then I check the source issue within if/else
  • and add destination issue branch for each option

--> see screenshots below.

For better understanding of the use case I built:

I have a Service Management Project "ITSM" and a software project "JT". Within my ITSM project I have issue type "Service Request" and "Incident".

These issues could both CAUSE a task in my "JT" project ( eg. Incident (ITSM) CAUSES task (JT) --> indicent is source issue, task is destination issue)

So my rule triggers whenever a link of type CAUSES/IS CAUSED BY is created. When the source issue is an "Incident" the rule branches for the destination issue (which is the task) and edits it according to your requirement (eg. YES).

Else if the source issue is a Service Request the rule branches for the destionation issue as well but this time writes NO.

(In my screenshots is the field "Number 1". This needs to be changed according to your requirement).

 

Hope this was helpful.

Best
Stefan

 

grafik.png

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events