We're currently using one project for Customer Service reported bugs, which contains all the customer information needed to triage and resolve the problem. Many issues get fixed by CS, but some are bugs that need a developer to look at them. When that happens, we move them to a DEV project, which contains less information so that it's cleaner for the developer. The problem, is that between moving an issue from CS to DEV, there is a prioritization exercise that requires that additional information to decide which bugs are more important.
So my options are to create a new project for prioritization with all the fields. Which I don't love, but could be done, or to use a workflow to show where an issue is at.
My question is, could I create a custom status for when the bug gets to development that automatically hides all the extra information they don't need? If yes, how? If no, I'd love to hear other suggestions.
I don't think there is any clean way to do this.
One way might be to clone the original bug and move the cloned issue to DEV. A link is created between the original issue in CS and the cloned issue in DEV. The person prioritizing the issue for DEV can use this link to see the original information and decide on the priority.
Also, CS can see the original ticket, can see the status of the linked ticket, and can update the customer.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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