The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
In every version, we update issues with Fix version, suggesting the version in which we intend to release.
But in these versions, there are some epics / stories that are half cooked [code present but goes into production as masked].
To track these items we intend to use Affects version field - when the epics / stories are brought into backlog and fix version to track the actual completion / release of them.
But there has been severe resistance from some members arguing that Epics cannot be tagged with affects and fix version.
I would like to know what is the intended use of these fields specifically for epics & is there a better approach to my problem. Sorry for the long question, appreciate your answers.
Regards
Sam
👋 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...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events