nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Access value from specific issue in Jira

Benoit_6lqhxf

Hi all,

I am trying trough smart value to access a specific value in a specific issue in Jira to apply or add to the current issue value.

Example: {{custom numeric value}}*{{DF-1234.custom numeric value}}

Thank you

Accepted answers

All comments

Mykenna Cepek

Take a closer look at the documentation on using Smart Values:

Stefan Salzl

Hi @Benoit ,

to better understand all requirements could you please describe a use case?

when should this happen? (what event/issue is the trigger?)
is there a relation between the 2 issues?
what does "specific issue" mean? how should this issue be detected?
What exactly is the question / information you need?

thanks in advance.

Best
Stefan

Benoit_6lqhxf

There is no relation between the two issue.

I use some issue in a different project as constant, per example forecast of sales. I do not want to add forecast of sales in every issues. but I do want to use it as a factor of a value in the newly created or modified issue.

Thanks

Benoit_6lqhxf

Hi, I do have read all the documentation, and I can't see anywhere my use case.

issue.Invoice Amount per example refers to the trigger issue, but I want to check value in a different issue not related with this one.

How do I do.

Thanks

Stefan Salzl

Hi @Benoit ,

As you want to refer to an issue in another project the rule needs to be a multi-project or gloabl automation rule.

to gather information from that other issue you can use the "look up" action and refere to that issue/field via smartValue {{lookupIssues}} (see screenshot)

Please let me know if this helps.

Best
Stefan

Benoit_6lqhxf

Sorry, I forgot to tell that I am on server Version, therefore no lookup function. Don't blame me, Atlassian cancel their Server platform 4 months after we bought it. (Sooo much frustration and additional cost to us because of that)

Thanks

Bill Sheboy

Hi @Benoit

You note referencing a field in a specific issue, such as {{DF-1234.custom numeric value}}

Is that field's value static or dynamic?

If that value is static have you instead considered hard-coding it in the rule, or storing it an Entity Property rather than trying to access the value in another project?
If that value is dynamic, you could trigger the rule so your DF-1234 is always the triggering issue, and then use branching within the rule to access the data as fields of {{triggerIssue}}

Kind regards,
Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

custom-field

cloud

automation

smart-value