This issue has been created
There is 1 comment.
 
 
JIRA Components / cid:jira-generated-image-avatar-cae7b575-dedd-4c6b-b743-cffd15ea78f7 JIRA-110 Open

Jira macro should honor all issues provided as a list of issues

 
View issue   ยท   Add comment
 

Issue created

 
cid:jira-generated-image-avatar-8e4b1e92-2627-467a-8c03-0f84bab99cd5 Anca Luca created this issue on 23/Feb/26 16:32
 
Summary: Jira macro should honor all issues provided as a list of issues
Issue Type: cid:jira-generated-image-avatar-cae7b575-dedd-4c6b-b743-cffd15ea78f7 Bug
Affects Versions: 11.1.2
Assignee: Unassigned
Components: JIRA Macro
Created: 23/Feb/26 16:32
Priority: cid:jira-generated-image-static-major-472a476d-da29-4968-a2da-430526807095 Major
Reporter: Anca Luca
Description:

One case for this need is the one described in issue JIRA-102.

Steps to reproduce:

  • add a jira macro, with the source parameter set to list (or unset, as the default is list)
  • put a list of issues in this jira macro (or a single issue)
  • on jira instance side, change the access rights to some of the issues from the list for the service user, or delete some of the issues

Expected result:

  • in the display of the jira macro, something should be displayed for each of the issues from the issues list - either its metadata and status, or a message that it cannot be found / cannot be accessed, depending on the case, maybe a link could be built for it automatically from the issue key and jira instance URL, etc.
  • Note: there could be a parameter to control this behaviour, but the default of this parameter should be that by default the macro displays something for each issue provided explicitly

Actual result:

  • for issues that are not accessible or don't exist, the macro displays nothing at all (empty result);
  • a special case is the case when there is a single issue in the list, for which the macro could endup displaying nothing with no explanation.
 
 

1 comment

 
cid:jira-generated-image-avatar-8e4b1e92-2627-467a-8c03-0f84bab99cd5 Anca Luca on 23/Feb/26 16:35
 

The current implementation of the jira macro is handling the JQL data source and the list data source in a similar way, it's converting both of them to a jql query, runs the query in jira and displays the results. The list of issues becomes a jql query which is a search for issues that have those keys.
Of course, an issue that doesn't exist anymore won't appear in the results and thus nothing would be displayed for it. We should add a special handling of the list data source, to ensure that we honor all elements from the list.