Setting up Query Issues custom field

[Justin Leader]

Howdy!

I need help setting up query issues plugin.

Here's the situation, I have three types of issues, Platform, SW Stack, Mod.

I've set up the query issues so that from the platform issues edit screen, multi linking custom field "SW Cycle Stack" can multiselect from any of the stacks.

Similarly, from the SW Stack issues, I can multiselect any of the mods into "MODs in stack."

Now I have "Add MODs", a multi linking custom field, and I want it to appear on the Platform edit screen, and only present me with MOD issues that are not associated with any of the SW Stack issues that are associated with the Platform issue I'm editing. So it has to check two layers of connections.

Here's the config I've got so far... Please help! Thanks!

[M. P. · Accepted solution]

• You need to add "Query issue related custom field"
• Give a name for example "Test Case"
• And link to Issue Type that is primarly linked to this Test Case
• In your "Related Fields" you will get "Test Case" displayed under Custom Field
• In Configuration you have to add following Query: issuetype = "Test Case" and Requirement = RLINK. In this Case Requirements are your [linker_custom_field], this means that internally your Test CAse is linked by Requirements and you can find Test Case through Requirements.
• Through Issue Navigator , you will be able to add "Test Case" field
• After if you will search for issuetype = requirements you will get all Test Cases for this Requirements
• Conclusion, you can display only those fields which are linked to one particular issue. If for example Requirement has more of those links, you can display them all

[Andrey Markelov]

Hi Justin,

Could you clarify which fields related to which issue types?

-- Andrey

[Justin Leader]

Sure Andrey, thanks.

Platforms are comprised of SW Cycle Stacks, and I can label each Platform with several Stacks.

SW Stacks are comprised of MODs, and I can label each Stack with several MODs.

Is that the info you wanted?

[Andrey Markelov]

No, it's enaught. I will think about few hours

[M. P.]

Additionally if you will combine Query Issue Custom Field Plugin with AM Utils Plugin https://marketplace.atlassian.com/plugins/ru.andreymarkelov.atlas.plugins.utils

you can create queriy inside of another query for parents and childrens:

• issue in issuesSubtasks ("issuetype = \"ParentName\" and [linker_custom_field] = RLINK")
  gives us a List of Subtasks of the Parent
• issue in issuesParents ("issuetype = \"ChildName\" and parent= RLINK")
  gives us a List of Parents of the Subtask

And again even here [linker_custom_field] is a field that is a linker for parent, if for example Test Case is a Parent for some Issue and is linked by Requirement, than query would look like this issue in issuesSubtasks ("issuetype = \"Test Case\" and Requirement = RLINK")

[Justin Leader]

Who's the man?? You are! Thanks dude. One other thing, much less important. It wasn't clear to me (although I haven't delved into code) what the related fields really were supposed to do and how to use them. The example given in the docs was rlink|AAA|"Fieldname" so at some point could you point me to an explanation?

Fantastic plugin; very focused; good work!

[Andrey Markelov]

For current versions you can use: [JQL part] AND [linker_custom_field] = RLINK

for related fields. During processing plugin will change RLINK to current issue key. So you will get all related

[Justin Leader]

I'm still confused here: Can you give an example for this related fields query? Can I use it to display field X from issues A,B,C on issue D's page? I don't understand what [linker_custom_field] is supposed to do here; is it referring to itself? Or just to other linker fields the plugin has created?

[Andrey Markelov]

I will write a new function to the next version. Will be done during 2-3 days.