Improve messaging on create Forms page when work-item has issuesecurity added

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • Component/s: Forms - Create
    • None
    • 3

      Currently, if a Jira project has issue security added (both TMP/CMP), and a Jira ticket is set to the security Level when a form is submitted by a user.

      The forms page displays an error message.
       
      The current message is not clear enough and is presented as an error, which causes users to submit more tickets in confusion.
      Improving the messaging on the create Forms page when a work item has issues added would be helpful.

      {
          "errors": [
              {
                  "message": "Issue is unavailable.",
                  "locations": [
                      {
                          "line": 6,
                          "column": 7
                      }
                  ],
                  "path": [
                      "createJiraBusinessIssueByForm",
                      "item",
                      "issueKey"
                  ],
                  "extensions": {
                      "errorType": "ISSUE_UNAVAILABLE",
                      "statusCode": 404,
                      "classification": "DataFetchingException"
                  }
              }
          ],
          "data": {
              "createJiraBusinessIssueByForm": {
                  "item": {
                      "id": "ari:cloud:jira:<cloudId>:issue/<IssueId>",
                      "issueId": <IssueId>,
                      "issueKey": null,
                      "__typename": "JiraWorkManagementViewItem"
                  },
                  "success": true,
                  "errors": null,
                  "__typename": "JiraBusinessCreateIssuePayload"
              }
          }
      } 

       

            Assignee:
            Unassigned
            Reporter:
            MonaS
            Votes:
            6 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: