add my own custom label for jql subset

[Anna]

Hi there,

I need to combine a few filters through logical OR and need to differentiate between different filters.

For example, in select statement I can use

select 'my label 1', column1 from table1 where condition1

which will give output of 2 columns with value 'my label 1' in the first column.

How i can organize a similar approach with jql? I don't see any possibility here as it extracts existing values from the backend and functions only as "condition1" in select example above. 

[Trudy Claspill]

Hello @Anna 

JQL in Jira is only for specifying the conditions you want to apply when selecting issues and the order of the output. It is not used to specify the columns that will display in the output.

To learn about changing the presentation of the search results (defining which columns you want to see in the output) refer to:

https://support.atlassian.com/jira-software-cloud/docs/change-the-view-of-search-results/

Since the function is designed solely for retrieving issues, you don't specify a source "table".

For more information on how to use the issue search capabilities you can refer to this documentation:

https://support.atlassian.com/jira-software-cloud/docs/search-for-issues-in-jira/

Details about advanced searching using JQL can be found in the subset of documentation here:

https://support.atlassian.com/jira-software-cloud/docs/use-advanced-search-with-jira-query-language-jql/

Can you provide a more specific example of what you would want for "condition1"? If you can provide a more specific example of what you are trying to retrieve we can provide more relevant and detailed advice.

[Anna]

Hi Trudy,

Thanks for the reference links. 

I was able to solve this issue through trigger. My objective was to identify all defects which are still open and group them by different scenarios, depending on Assignee (can be developer, QA or unassigned) and commits (>0 then taken care of, =0 no changes from developer yet). The trigger will check each defect for Assignee role and commits count then will Edit a custom field in the issue to identify scenario/rule. After trigger run, I can sort by that custom field to see all possible groups of different scenarios for my issues. A long way doing, however gives an ability to group through custom field.

Also, the option "This rule should send emails" in Edit Issue action was unchecked in the trigger to stop sending emails as the rule will run on a daily basis making calculation and editing the custom field.