Dear all,
I'm currently seeking for a possibility to depict a process chain in JIRA.
The background is, that we want to describe exactly how a deployment of our software has to be done and which milestones have to be passed (and what to do if the product doesn't pass a milestone), e.g. internal QA finished -> acceptance tests -> acceptance tests finished -> deployment on testing -> ... -> deployment on live servers.
I know that I could create a project for this with a special workflow where a deployment issue could be transitioned through the status, but the issue should actually be contained in an existing greenhopper/JIRA agile project.
Any ideas on this?
Thanks and best regards,
Marcel
Community moderators have prevented the ability to post new answers.
I am not sure if i understand your question. But will try to help
1. Workflows: What i recommend you is create a new workflow exactly how you want it to be. Only points to consider is the difference between statuses and transitions. For me statuses are attributes where an issue spends a considerable amount of time e.g. in your case Acceptance Test and transitions are what we define as paths leading between one status to another and where an issue spends an infinitesimal amount of time e.g. in your case i would define Acceptance test finished as a transition leading out of status Acceptance test and leading into status Deployment on testing. If you keep these differences in mind you will be able to come up with a workflow.
2. Issues are always within a projects; you can never have an issue which is not assigned to a project; so your second concern is a non issue.
3. You can map any project issues on a greenhopper board. What i recommend you is to go through the documentation of greenhopper to familiarise youeself a bit more with the concepts.
Rahul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Seems like you're on the right track. Why not just create the workflow as you talked about it and apply it to a new issue type within the same project? Call the issue type something like "Deployment Task."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, this works. Simple though :-)
Btw: sorry for the late answer, I'm just very busy at the time...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.