Why is it useful?
Our Product team uses tags in Aha and labels in jira to help in planning which team works on which requirement / user story, to make sure that one team working in the release is not over-burdened.
Sometimes one team works on an entire features, but there are times that multiple teams work on the feature, splitting up the stories. For this use case, it would be helpful to have tags on Requirements, and to sync them with the labels in jira (which we already do for Features).
Who would benefit?
Both Product Managers and Engineering would benefit, having the same information (labels on user stories) visible in both Aha and jira.
Now, the Product Manager has to wait until the feature/requirements are pushed to jira, before they can assign a label to the user story. And they have to remember to transfer the label at the epic/feature level to the user story where applicable.
How would it work?
An additional field (tags) would be available at the requirement level, and would sync with labels in jira.
|Release time frame|