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

advanced json edit condition with issuelinks not working

Hi,

the use case is that i would like to update an issue field with some of its *specific* link issue type keys. for example, issue A is blocked by issue B and relates to issue C.

i want an issue field of A to contain the value B but not the value C. 

im using this in the json edit:

{
"fields": {
"customfieldName": "{{#issue.issuelinks}} {{#if{{equals(type.id, 10002)}} {{inwardIssue.key}} {{/}}{{/}}"
}
}

 

i know that 10002 is the correct id that i need. i checked the json view of the issue, and also printed the type.id into the log.

 

however, using the syntax above, it doesnt add the relevant key.

1 answer

1 vote

Hi @ben friedman,

Does the following rule meet your needs?

Capture d’écran 2021-05-27 à 09.27.38.png

Looks like it does what you need:

Capture d’écran 2021-05-27 à 09.27.58.png

Hope this helps!

- Manon

@Manon Soubies-Camy  thanks for the reply, but not quite. 

i need to have that update on all the existing issues in the system that are already linked. 

The trigger cant be for a current linking that takes place. 

I have a manual trigger, that for BRANCH ISSUES: jql for epics + tasks != closed status.

i cant use another branch of linked issues within the original branch and i have to use the original branch to cover the existing issues.

thats why i wanted to use the json approach to pull information into the issue's UI. 

So would it work if you used a scheduled trigger instead of a manual one? It triggers the rule from a JQL query and then you can add a branch. You also can manually start the rule by clicking on "Run rule". Not sure to understand the functional need behind your question so my suggestion may be irrelevant.

Capture d’écran 2021-05-28 à 14.12.39.png

actually, the JQL under the scheduled should do the trick i think! 

Thanks :)

@Manon Soubies-Camy  im actually hitting a problem.

im getting only 1 value on the blocked issue and not a list from all the blocking issues. the blocked issue ends up with 1 blocking issue in the text field. 

in the last action of edit im using ' {{issue.blockers}} {{triggerissue.key}}'

i think that this is since the blocked issue is empty at the beginning and all blocking issues use that instance. i tried to to refetch issue within the FOR, but that didnt help. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
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...

172 views 6 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