I am DevOps and a part of my role is adminstrating Jira/confluence project requests, scheme/ workflow creations, user admin etc.
I have a request from a Business analyst that she requires a new project that can keep track of bugs for a particular project that is apparently going to close off. (she is also moving left over backlog items to this new project)
To my understanding. is there a point in creating a project jsut to keep track of bugs for a another soon to be closed project. More over shoulnt all backlog items be closed anyway in the initial project? (should they keep track of the logs in the first project without closing it?)
I don't think that's unreasonable. But I would question why you're being asked to shut down a project that has work that needs doing in it. Surely those should go on in that project until they are fixed?
I don't think there's anything wrong with another project absorbing outstanding bugs etc, but I would question why you're shutting down a perfectly good project if the new project is just there to hold the bugs from the old one.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.