Need recommendation

Question

Hello All!!

I have a request from one of my development teams to create a proyect where to treat new requirement asked by Operation team.

Operation team is going to create the requirement and the anaysis team is going to evaluate if it is possible, sent it back for review to Operation team  and then after operation team approve it, the requirement is going to be sent to development team in order to be developed.

Once developed, the requirement is going to be set ready to UAT and the process end once uat is approved and close once the requirement is in Production environment.

You probably suggest to implement in a service desk, but develepment team want to track in the roadmap this requirement.

So... they asked me to implement this circuit in jira software using only an epic as the issue type, just to be able to be able to see epic in roadmap (we have standard plan, so we can only add start and end date for Epics).

What are your suggestions?

Thanks in advance

Ro

Rosana Casilli · Answer

Hi @Jack Brickey

Thanks a lot for your recommendation..

I have realized that I have written service desk but I meant work management. :S

I like your approach!

We have already the development team working with different proyects for different product development, but they wanted to have another software project because they don't want to purchase any additional license for Work Management (If so, we will need aprox 25 licences to start with) so they asked me to create another project as I have detailed above.

They want a kandban board to be configurable,--> it is not availble in work management

They want a roadmap present in both products, but not that flexible in the jira software proyect since we have standard edition.

So I am trying to convince them to have the proyect in work management, and they still can work in issues transition them or assigning from List opcion in the navigation menu (if they are not comfortable with the kanban board) .

Let`s see what they say!

Jack Brickey · Answer

There are a number of ways of implementing this however based on what you have stated here I might do the following.

create projects:

* Product Requirements (business template)
* Product Development (software template)

product requirements bullet points:

* issuetype - Feature Request 
* workflow - New > Assessment > Done
* Resolution - use this field to convey decision: approved, rejected, cancelled, etc.

use Automation to trigger on feature request moving to Done. If resollution = approved then create your Epic and any stories.

Development team can manage their backlog and development as appropriate.