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

Improve UI error messages related to workflow validators.

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • None
    • 2
    • 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.

      Problem Definition


      When an issue doesn't meet the criteria of a workflow validator the error messages aren't intuitive to resolving the validation issue.

      i.e.

      • Have a workflow validator that checks that the parent status is in a particular status for a subtask on a workflow.

      If you try to create the subtask you get an error that it has unsupported content in an issue field and to contact your admin to check the log file for specific info.

      Error creating issue:

      We see the exact error in the logs:

      com.atlassian.jira.exception.CreateException: Transition is not authorized because current Issue's parent Issue should be in one of the following statuses: [To Do, Selected for Development, Reopened, Scheduled for development, In Progress, Backlog]


      Suggested Solution

      Provide more specific information relative to the validation error via the UI instead of the logs similar to a workflow helper such as where is my field available from the issue view to identify the cause.


      Workaround

      1.) Reproduce the issue.
      2.) Tail the logs at the time or check the general time frame the issue occurred in the logs.


        1. wkfw.png
          wkfw.png
          24 kB
        2. error.png
          error.png
          40 kB

            [JRASERVER-59736] Improve UI error messages related to workflow validators.

            Why is this Won't Do lol... This is clearly a bug.

            Steven Behnke added a comment - Why is this Won't Do lol... This is clearly a bug.

            Atlassian Update – 29 March 2018

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Jira Product Management

            Gosia Kowalska added a comment - Atlassian Update – 29 March 2018 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Product Management

              Unassigned Unassigned
              jcastro Jose Castro (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: