We recently made the affect versions field mandatory and what this has caused is that the projects which do not have any versions defined are no longer able to raise issues.
What the way to resolve this without rolling back the change?
Secondly, how do i identify the projects which do not have a version in it( manually checking is very tedious)
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/
The roof is on FIRE… network outages, broken processes, upset clients and employees. Each day seemed to bring more and more issues. Incidents were communicated via email, messengers (skype or teams) ...
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