We have our kanban board for a next gen project and have added child tickets but they do not show up in the board, only as an icon on the parent ticket. Ideally we want to keep this hierarchy of tickets that lead back up to an epic but show them all so we can get a better view of what is going on.
I would roll back the change.
Use Field Configuration Schemes to create a "Versions are Required" scheme that project and issue type combos can elect into without affecting the entire population.
There are a rnage of use cases where version makes no sense, especially Affects Version (anything not a bug!)
Forcing fields does not mean accurate entry. In fact studies show you are more likely to get false data when you force users to enter fields that may see as irrelevant, or unsure.
The fastest way to find projects using versions is via the REST API. Get a list of all projects, then for each grab the version info. https://docs.atlassian.com/software/jira/docs/api/REST/latest/
Thanks Eddie, the explanation helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.