Error setting Epic link from a linked issue
When I try to set Epic link field using by the "Read field from issues returned by JQL Query" or "Read fields from linked issues or subtasks" post functions, I get a "plugin being incompatible with this version of JIRA" error. Our JIRA is JIRA Software V7.1.6 The settings and error messages attached.
The post function works well when I used the "parsed text (advanced mode)" as a source instead of "field in selected issues". But when I injected the Epic link field code into the parsed text, the post function failed again.
Comments (7)
-
repo owner -
reporter Hi Fidel,
-
The current isse type is Task, and it is not included in query
-
I expect only one issue in the test case, but later maybe more. I tested the query and it gives only one issue
We use the latest, 2.2.34 version.
Regards,
Tibor
-
-
reporter Hi Fedel,
Meanwhile I did some tests, and I find out, the post function gives back the Epic's issue key as "Epic link" (^%{10006}), but the target issue expects the "Epic name" as "Epic link" Maybe this is the problem?
Regards
-
reporter I was right. With this query:
issueFunction in linkedIssuesOf("issue in linkedIssues('%{00015}') and issuetype in (Story,Hibajavítás,Bug,Fejlesztés)","has Epic")
and using "Epic Name" as source, and "Epic Link" as target, the function works as I expected.
-
repo owner With that JQL query you can obtain more than one issue, and then you are overwriting "Epic Link" more than once. It doesn't hurt but is inefficient.
I recommend you to use an issue list expression instead of a JQL query, like shown in the screenshot:
Issue list expression is:
first(linkedIssues("has Epic", filterByIssueType(linkedIssues(), "Story, Hibajavítás, Bug, Fejlesztés")))
It also has the benefit of not depending on a another plugin for JQL functions (Script Runner in this case).
-
reporter I tested it and works well. Many thanks for the advice and quick help.
-
repo owner - changed status to resolved
Just released version 2.2.35 supports setting Epic Link, not only with Epic Name, but also with other issue's Epic Link or writing a string value containing the issue key of an Epic issue.
- Log in to comment
Hi Tibor,
3 questions:
Thanks