Hi there
I have a scenario in which I need to create an issue for one of our technical teams (Project B), based on an inserted label in another project (Project A).
While I can do the most of it, I don't know how can I mention the key of the original issue (A) in the description and/or summary of the new issue (B).
Do you have any ideas?
Thanks
@Tal Stanek if that is not the case, then you can use {{triggerIssue.key}} - assuming the original issue is the one that triggers the rule. But as long as you are not using some branches in your rule, {{issue}} should also work.
Thank you @Adam Rypel _MoroSystems_
I will try, but I think that the smart value {{issue.key}} will show the issue that will be created via Jira Automation and not the original one.
I'll update once implemented and tested
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Tal Stanek ,
I suppose you are using Automation for Jira?
You can use a smart value in the summary / desc of your target issue, see more on that here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/
You basically just need to use smart value {{issue.key}} (or even {{issue}} should be enough I think) in your text and it should display the key of original issue. You can also use {{triggerIssue}} for more clarity.
Hope that helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.