-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
6.2.1
-
2
-
Severity 3 - Minor
-
Summary
The error messages provided by the Jira Issues Macro do not always match up with the messages provided in the Jira UI. For example, if you perform a JQL query for a status that doesn't exist, Jira will give an error stating the value doesn't exist for the field 'status' but the Jira Issue Macro in Confluence will show JIRA project doesn't exist or you don't have permission to view it.
Environment
- Tested with Jira Software 7.3.6
Steps to Reproduce
- Create a project in Jira, TEST, create an issue (in this example I will use To Do)
- Add a Jira Issue Macro to Confluence with the following JQL:
project = Test and status = "To Do"
- Save the page
- In Jira, rename the Status to "Will Do"
- Project settings > Workflows > Click the Pencil icon under actions > Click To Do status > Edit > Save
- Refresh the Confluence page
Expected Results
The Jira Issue Macro table will display the message that Jira would:
The value 'To Do' does not exist for the field 'status'.
Actual Results
The Jira Issue Macro table displays:
JIRA project doesn't exist or you don't have permission to view it.
- depended on by
-
CONFSERVER-60129 Cannot sort newly created Jira custom field columns in Jira issues macro
-
- Long Term Backlog
-
- mentioned in
-
Page Loading...