Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-85557

If we don't want to add any information on the Priority field, Jira should bypass this field and not generate an error.

XMLWordPrintable

    • 2

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      If we don't want to add any information on the Priority field, Jira should bypass this field and not generate an error.

      Today, if we associate the priority field with a screen, and add to a workflow, even though this field is not mandatory, we must fill it in with data.
      If we don't put any information on the priority field before transitioning the issue we will receive an error: "We couldn't update XXXX."

      This we will find on the Devtools
      message: [Limited to 100 per PT1M] No data returned for operation `makeTransitionuseMakeTransition_makeTransitionMutation`, got error(s):
      Variable 'v0' has an invalid value: Field 'id' has coerced Null value for NonNull type 'ID!'

              Unassigned Unassigned
              b60c2e526cc5 João Carlos Montanha Zurobski
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: