In the default Jira Workflow, the Resolve Issue Screen is the only screen where you can set the Resolution field for an issue, and this screen is only used for transitions to the Resolved and Closed statuses. In your own workflows you are responsible for making sure that the Resolution is set.
Thanks for your mail gracy. This workflow is having prime focus on release planning and management.
Release management is the process of managing, planning, scheduling and controlling a software build through different stages and environments; including testing and deploying software releases. For tracking the whole process with better visibility this workflow has been designed. Implementing this workflow will help the organization in many ways: 1. This workflow is best for the teams involved in release management process which are geographically located at different places. 2. Maximise the efficiency of your organization with minimal outlay with our preconfigured Release Management workflow. This workflow removes a lot of manual effort and issues that occurs in communicating while shipping task details in release management process. 3. It makes collaboration better by utilizing predefined workflow. 4. It reduces time by providing list of specific tasks for each and every role and real time notification to every role. 5. This workflow consists of many predefined rules like predefined permission policies for every stage, assignee restriction etc. 6. Also the screens are attached with each stage that will be filled only by concerned person only. 7. At any time, admin may customize this workflow in terms of States-Transitions- authentication rules-changes in users mapped with Stages-Screens etc. 8. Scope of issues are very less, as information is circulated properly to each and every one, so if some flaws remain same in build or environment, it will be caught and can be resolved before final release.
In the default Jira Workflow, the Resolve Issue Screen is the only screen where you can set the Resolution field for an issue, and this screen is only used for transitions to the Resolved and Closed statuses. In your own workflows you are responsible for making sure that the Resolution is set.
ReplyDeleteThanks for your mail gracy.
ReplyDeleteThis workflow is having prime focus on release planning and management.
Release management is the process of managing, planning, scheduling and controlling a software build through different stages and environments; including testing and deploying software releases.
For tracking the whole process with better visibility this workflow has been designed. Implementing this workflow will help the organization in many ways:
1. This workflow is best for the teams involved in release management process which are geographically located at different places.
2. Maximise the efficiency of your organization with minimal outlay with our preconfigured Release Management workflow. This workflow removes a lot of manual effort and issues that occurs in communicating while shipping task details in release management process.
3. It makes collaboration better by utilizing predefined workflow.
4. It reduces time by providing list of specific tasks for each and every role and real time notification to every role.
5. This workflow consists of many predefined rules like predefined permission policies for every stage, assignee restriction etc.
6. Also the screens are attached with each stage that will be filled only by concerned person only.
7. At any time, admin may customize this workflow in terms of States-Transitions- authentication rules-changes in users mapped with Stages-Screens etc.
8. Scope of issues are very less, as information is circulated properly to each and every one, so if some flaws remain same in build or environment, it will be caught and can be resolved before final release.