For our particluar instance, FIxVersion doesnt make sense to have at the subtask level. We thought that maybe if we create a new screen, screen scheme, issue type screen scheme, issuetype and issue we would make this all work. Alas, it doesnt.
All I want to do is remove the field across all projects without having to digest all the different scheme hierarchy, etc.
Any ideas?
When you mention above that creating a new screen, screen scheme, etc didn't work - how didn't it work in your environment?
For classic projects - you'll need to either:
^ As each project has a new screen, screen scheme and issue type screen scheme by default, it would be arduous to do this for each one.
I would consider how much variation you have in screens / schemes and create a smaller number to apply to your projects. This means when changing one it will be easier to effect multiple projects in future.
For next-gen projects which have Releases activated - you'll need to go into each individually and...
^ This doesn't turn them off, but means one cannot be edited onto the issues.
Ste
Show up and give back by attending an Atlassian Community Event: we’ll donate $10 for every event attendee in March!
Join an Atlassian Community Event!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.