We currently use Priority field to give the severity of an issue (high, med, low). I'd like to have another field in to help determine the business priority to fix a bug. For example, if you had something such as a spelling error in your UI which doesn't impact the usability of the product, but would be a big issue for a customer to see. In this case, we would change the bug priority to high to ensure it gets in the developer que to get fixed. I’d like to have a field added to the jira bug that highlights the business priority to fix an issue. Thanks
I would actually switch your method above where I would create a "severity" custom field and use the Priority field as intended for priorizatation. That way new folks added to the team would not get confused. But it sounds like eiither way that you go you're trying to use a combination of two fields where there is only one priority field in JIRA.
You could hijack other fields like the story points field to show that if you didn't want to create a custom field. But you would need to be very clear in your documenation and communication of how that field is being used.
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG