To report a Bug, Customers with a commercial support license should raise a support case with Atlassian Support. They will work with you directly to collect the details Development needs and craft a detailed Bug report so it has the best opportunity to be fixed.
Other Customers should ask a question here on the Community site. When the nature of the problem is clear, an Atlassian will either raise a Support request for you or report the Bug at jira.atlassian.com.
@Morgan Knicely I was able to post a bug, but I am not able to find the syntax we can use for highlight the text: bold face, source code, etc. I realized that there is no way to edit the information we published, so I would like to be sure about how to use the syntax before sending a comment. Thanks. David
You'll get a broader range of answers if you raise this as a new question, but each Jira installation hosts a document with details of the wiki format. Here's the one for our public issue tracker, jira.atlassian.com: http://jira.atlassian.com/secure/WikiRendererHelpAction.jspa
I am adding a little elaboration for everyone that sees this post as to why this is the case, as we have had a few questions pop up recently about this thread, and the process we follow for bug creation, that we wanted to make sure to clear up.
Atlassian decided to remove the option to create bug reports directly and funnel the bug creation process through the support teams to provide a better experience to everyone with the main focus being to reduce the number of duplicate bug reports created for the same issues, which was causing a lot of trouble for all.
With the ability of everyone being able to create bug reports using varying formatting, wording, and styles to relay the information, the overall outcome made it difficult for others to locate and identify a preexisting error leading to an increasing number of duplicate reports in turn causing more and more requests to be lost in the noise.
Ultimately, duplicate issue creation would cause confusion to both end users of the application and the developers as to which ones were actively being worked on, which ones are still relevant to current versions of the application, and wether or not a bug had already been fixed on another duplicate bug report that had not been linked as a duplicate in the issue tracker during the triaging process (i.e. it got missed due to volume), and in many cases the behavior could not be replicated without additional environmental variables that come into play such as the browser used or network settings.
We have created this process to go through the support portal as a first step for information gathering to verify reproduction steps and errors, and assist in searching for existing reports for the behavior to prevent duplication, and then create the new Bug reports on your behalf when no preexisting report can be located, following a standardized bug creation template to relay the information on the request for a easy to digest and recognizable data format.
There will always be Bugs in the software and there is no way to avoid that, but we do want to reduce that number as much as we can. So if you encounter any behavior that you think is a bug please do call it out and contact our support teams to take a closer look a support.atlassian.com, and if you do not have a valid support license, you still have access to the community so please do post the information you find here on the community.atlassian.com to bring additional attention to the issues so that either a Community Leader or Atlassian can jump in to help out.
I'm under support, and I just searched the open suggestions for a particular product (Bitbucket Server), and it dropped me straight into a complex JQL query -- which was a good filter -- but then to actually search through the 1600+ issues I need an intelligent full text search engine (i.e. Google).
It wasn't clear where or how to do that, and I certainly wasn't going to use JQL, so I would suggest this UI discourages me from finding existing issues that I can just upvote, and encourages me to create a duplicate.
My solution was to use the Export menu to dump all issues into a massive 20MB web page and use my browser's search to locate items, and voila I found the suggestion I was going to make very quickly.
to me it sounds a bit funny that the company which is providing a solution for Bug tracking (and filing bug reports) is not able to make it public in a way that duplicates can be handled in a manageable way :)
We are using JIRA as product in our company also with access for our customers and they can raise issues as much as they want...and yes we are also dealing with the situation of a certain problems reported many times. But with JIRA we are able to accomplish that.
The disadvantage I see raising a question in this forum vs. raising a JIRA ticket directly:
And maybe more.
Just rethink your decision, improve your great product and make identifying duplicate just easier :)
Tell me about the bug. If we can document the steps to reproduce this bug in the product/version, then I will create the bug ticket on your behalf if need be.
Community is one means in which we provide customer support as well. There are also other channels, but not everyone has access to these. Everyone with an account on Atlassian has access to Community.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events