We do have several projects (25) where most of them are based on the same projects. Each of them may have multiple versions.
When we find a bug, it's a mess to determine which version is affected by what, and having to clone a issue 15 times is probably not the right way to go.
What are the best practices for such situation? Thank you!
You mean you have about 25 projects most of them based on the same *products*? With multiple versions on projects?
Perhaps you should think of a complete redesign of your configuration management
At least a component owner should know which bug affects which version, no? Then you always could assign bugs to the component owner who then needs to decide where to clone the bug to so that other projects may also investigate about the impact on their project.
Yeah, I know that 25 "different similar" projets could be better but there is some reasons why it is done like this.
In fact, we made our configuration so we have a compile time configuration instead of a run time configuration.
And about JIRA project, I understand that you would put everything in only one project, where this project has several version partialy related. Am I understanding well?
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG