Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,298,501
Community Members
 
Community Events
165
Community Groups

What is the best way to guide bug issue creators on Jira Software ?

Hi,

it seems to be a pretty usual question but surprisingly I didn't find any efficient, simple and not insanely expensive answer to that.

Our 12 developers team uses Jira Software for its daily tasks management. We'd like to invite 3 support members to the project so that they can report Bug issues. The only condition is that we want to provide them a little bit more guided issue creation form with questions like "What is the browser ?" "What is the impact for the user ?".

Idealy, the Forms feature for Service Desk is what I want - but it seems over-complicated and expensive to create a whole new Service Desk project just for 3 people creating bugs on Jira Software.

Being a small team - how would you allow a small customer support team to efficiently create and track bugs in Jira Software ?

1 answer

Can you use the issue collector under Project settings by any chance?

"Collects the environment data of the user, if they consent to it being collected. This data includes the browser type, screen resolution, referral header, and URL where the feedback was collected."

I think this should be helpful?

If you use the custom template, then you can add any fields you want in there.

 

This need to added as a small JS or HTML snippet though, so you might want to connect it to a user account ID unless everyone that have access should be able to report bugs.

Hi Jimi

The custom form on the Issue Collector allows me to select issue fields I'd like to add to the form. It means I would have to add 20-30 fields to my Bug issue type, with no guidance or description on the fields.

If I accept that, Issue Collector would not be useful as I can add those fields to the Bug form inside Jira. But the issue is that adding 30 fields will add pollution to my views and I can't control the order/description/placeholder

May I ask why you would need that any fields and where the tests will take place?

I agree that the best place to add incidents and defects is in Jira itself, but I have not seen anyone needing that many fields :)

In my setups I place test fields in a separate tab and I usually have something like:

  • Steps to reproduce
  • Affects Version
  • Environment
  • Priority
  • Urgency
  • Browser (for FED testing)
  • Related Requirement (if known)

 

Then I use Components sometimes if it is applicable.

The only other option I can think of is setting up a Business project and use that for Incident management and then either update the filter in your regular JIRA project to also import those, or manually move them.

In the business project you can create forms like you can in Jira Service Management. Kinda :)

Like John M Funk likes this
John M Funk Community Leader Jun 14, 2022

I would recommend Jimi's last option as well. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,862 views 37 49
Read article

Community Events

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

Events near you