Release Issue Type

[GilK]

Hi,

We use jira and GH.

We have the SCRUM template: epic->story->task

We also have bug and improvement issue types.

We have few departments: HW, Embedded, server, mobile

Our testing process goes like this (per a release to customer, i.e. Release 2.5.4):

1. Development of few Epics in few departments (i.e. HW->epic 1, Embedded->epic 1, Server->epic 2)
Please notice that a single epic may be developed in few departments.

2. For each department there is few internal QA cycles (i.e. HW->QA cycle 1, Mobile-> QA cycle 4)

3. After all departments finish their development and internal QA cycles, the integration cycle begins (by a special Integration department), which tests all the departments deliveries together (i.e. Release 2.5.4 - All products->Cycle 1, Release 2.5.4 - All products->Cycle 4)

Of course, for each All Products->cycle n, there is another development cycle (to fix the bugs) and another few QA cycles (to verify them).

At the end of each integration cycle, the PO decides if we go for another cycle (dev->qa->integration) or we go out to the customer and release it.

Now, I need to represent those cycles in Jira with GH.

What would you recommend?

Thanks,

Janiv.

[GilK]

Someone has an idea?

[Nic Brough -Adaptavist-]

Step back from that, forget GH for now, and define a workflow that encompasses it all. When you're happy the workflow covers all your steps, then go back into GH to see how it overlays it all.

If your workflow looks too big, then consider splitting it and having separate projects or issue types and getting your people to move between them (i.e. "this needs QA, move to the QA project/issue type)

[GilK]

Thanks,

Can I move issues between projects? How?

[Jeremy Largman]

Yes, you can move issues so long as users have the move issue permission in the source project, and the create issue permission in the destination project:

http://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions