Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Using affects version for Epics

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

1 comment

Thomas Deiler Community Leader Jul 17, 2019

Dear @Gooty ,

I can understand your members about introducing an affects version to epics. "affects", from my understanding, is more intended to be used for bugs.

Fixed version for epics: You could also rename this to "Released Versions". Just naming. But in most cases you cannot assign it to exactly one version as it is to huge to be within one release.

The half cooked is only an issue on story level. As long as a story is done-done, it can be released. The container epic will stay most times half-cooked.

You could introduce a custom version picker field named "Part of Released Version(s)" and avoid using "Fixed Version".

Anyhow, I recommend sharing the information, gathered with this thread, with your team mates and let them be part of the decision.

So long

Thomas

Like Gooty likes this

Thank you for the quick reply Thomas. Appreciate it. 

Comment

Log in or Sign up to comment
TAGS
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

97 views 0 5
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