Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Hi Guys,
I Have 3 Issue type
issuetype A can triger create Issuetype B and C
the resuld is issuetype can be linked issue A-B and A-C
what I want automate link issue B-C because, if issue B changed status to drop, issue C change to Drop too.
I try to used JMWE Link issues to the current issue post-function in workflow B
and input
JQL expression : issuetype = "C"
after I test it,
Workflow issue B linked to issue C but not from issue C in same project where is it made
the question is, how to make specific project in JMWE-JQL?
How are you creating issues B and C? If you're using a JMWE Create Issues post function, then you can refer to
Best
David
Thanks for the reference,
I used JMWE for create Issue B and C
if Issuetype A created, it triger JMWE for creating Issuetype B and C
and it make link Issue A-B and A-C
what I need to make automate Link issue B-C
B and C create at same time
Regards,
Tyas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tyas,
if we assume that your current Iterator is something like:
[
{
"summary":"Issue B"
},
{
"summary":"Issue C"
}
]
which you use to create two issues, each with a different summary.
You can update the iterator to this:
[
{
"summary":"Issue B"
},
{
"summary":"Issue C",
"issueLinks": [
{"linkName":"blocks","toIssue":1}
]
}
]
This will automatically link issue C to issue B through the "blocks" link type direction.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @David Fischer ,
thanks for your information
like I discribe in my first question, I have 3 Issuetype (All of it different type)
but I thinks you assume B and C in same Issuetype,
I assume, that you are using : Create issue(s) post-function
and "Summary" in your script is from this one? (CMIIW)
And, issuetype A trigger create 2 another issue B and C ( same issuetype) with different summary
but mine is that Issuetype A can create Issuetype B and Issuetype C ( for now I can Create this by JMWE) and what I need to do is automatic to link an issuetype B and issuetype C.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
what I described works - you can create both issues using a single Create Issue(s) post-function, by selecting "Calculated" as the Issue Type, with this value:
{{it.issueType}}
and as the iterator, use:
[
{
"summary":"Issue B",
"issueType":"Issue type for B"
},
{
"summary":"Issue C",
"issueType":"Issue type for C"
"issueLinks": [
{"linkName":"blocks","toIssue":1}
]
}
]
and for the Summary field, use
{{it.summary}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks for the script
I follow your guide,
but, I get error
I try some condition for solving missing Issuetype from
example :
{{ issue.fields.issuetype.name }}
{{ issue.fields.issuetype.name == "Story" }}
please help find what is missing
Regards,
Tyas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Tyas Iglecias ,
sorry, I forgot to mention that, since the iterator script returns a JSON object, you need to check the "Iterator returns JSON" option.
Best,
David
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @David Fischer
Thanks for your guide it's work,
one more thing we missed was a comma,
and I check from your guide in confluence
its solved my issue
thanks very much
Tyas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have question,
How to link multiple issue with JMWE using iteration?
Example:
can you help me?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Rizky.Tuasikal did you read the documentation I shared earlier, and the example above?
If you still can't figure it out, can you open a support request with us: https://innovalog.atlassian.net/servicedesk/customer/portals
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.