Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-7159

Make Resolution field optional

XMLWordPrintable

    • 9
    • 41
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Atlassian Update – 13 Jan 2016

      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days.

      This suggestion is important for the JIRA development team, but we have not scheduled work and cannot provide an estimate on when it will be released. I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Daniel Franz
      dfranz at atlassian dot com
      Principal Product Manager, JIRA Platform

      Despite being set to Optional in the Field Configuration, the Resolution field always shows up as Required on any screen that includes it. This wouldn't be such a bad thing if it weren't for two things:

      1. it's not possible to select the Unresolved option (which would mean leaving the field empty);
      2. having any value set for Resolution makes the Issue to be considered resolved, and the Issue Key to be crossed out across JIRA.

      I would like to request that either the Required/Optional flag in the Field Configuration be made to apply to the Resolution field, or allow us to select a built-in UNRESOLVED resolution.

        1. sc 2.png
          sc 2.png
          120 kB

              Unassigned Unassigned
              abe7b7c5031a Joel Martin
              Votes:
              192 Vote for this issue
              Watchers:
              122 Start watching this issue

                Created:
                Updated: