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

The JIRA bug reporting process has too many roadblocks

XMLWordPrintable

    • 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.

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

      Reporting a bug against JIRA involves too many steps, including some unclear and some tedious, such that it’s almost not worth doing.

      Expected results:

      1. You can create a bug report for JIRA in the same way you can create a bug report for SourceTree.

      Actual:

      1. Attempt to create a bug against the JIRA project. Upon changing the type of report to “bug”, several fields disappear, including the Description field, and an infoblast appears with the text

        Help us fix bugs faster

        To help us get the right details and fix bugs as quickly as possible, submit your bug report in our support system.

        You can still view, watch, comment on, and vote for existing bugs by searching for them in this project.

        It has two buttons: “Report a new bug” and “Search for an existing bug”. Nobody has reported this issue yet, so click “Report a new bug”.

      2. Find yourself directed to Support System Hell. Find on page for “bug”—no results.
      3. Maybe creating an account will make the bug reporter appear? Create an account. No dice.
      4. Back on the Support System Hell Homepage, scan the items again:
        • JIRA Core documentation: not a place to report bugs, and also is JIRA Core different from just plain JIRA?
        • Knowledge base: not a place to report bugs
        • Community: not a place to report bugs, and probably part of the corporate Web disease that is the one-eyed answering the questions of the blind
        • Billing & licensing help: probably not helpful when it comes to reporting bugs
        • Product feedback: maybe…? No, wait, it just takes you back to the beginning of this mess.
        • Contact Technical Support: you don’t need additional people in the loop, especially ones who will, at worst, walk through the Uselessly Simplistic Official Support Flowchart to no avail, and at best, will report your issue without “helpfully” summarizing it and thereby losing potentially important information.
      5. The best possible outcome from the Support System Hell Homepage seems to be that the bug gets reported by tech support without modification, which means that you’ve gained nothing and wasted the time of a tech support employee.
      6. Grumble under your breath at the time lost creating a support account (which you’ll never use) and trying to navigate Support System Hell. Go back to the JIRA issue tracker, report the bug as a “suggestion”.

              Unassigned Unassigned
              669dd68e54d0 Harold Tessmann III
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: