An issue in Agile.Now
An issue in Agile.Now refers to a ticket that is required for deploying a software release. A ticket can be a user story, a bug or a support ticket that is initially created in the project management application.
Agile.Now dashboard is a single source of truth for all the work that the team needs to complete. Agile.Now dashboard. the list of all issues that must be completed in each environment in the project Agile.Now dashboard allows the users to track the progress of issues in the entire workflow on a single view.
Release version is the version where you plan on deploying a collection of issues and corresponds to the field value of the Fix version in Jira and Sprint in Azure DevOps.
Tips
When an issue is created, the user must make sure that the issue's release version is configured correctly in the project management application, otherwise, it does not appear on Agile.Now dashboard.
Workflow and Issues in Agile.Now
Workflow in Agile.Now is defined in terms of three main built-in categories which describe the team's working progress and the state of the issues. Mapping workflow ( ADD the linked ) feature in Agile.Now allows adapting your organization's existing workflow to Agile.Now workflow.".
The three main built-in workflow categories are as follows:
- To Do: It presents the list of all issues or tasks that are in queue for the team members to start work on them,
- In Progress: It presents the list of all issues or tasks that have been taken under work
- Done: It presents the list of all completed issues that can be moved to the next stage of the development pipeline.
The built-in workflow can be configured for multiple environments. This is beneficial where you have more than one Testing or production environment. The table below describes the development stages underneath each category.
| To Do | In Progress | Done | |
| Development environment |
|
|
|
| Testing environment | Testing stage | Testing stage | Testing stage |
| All other environments | [Environment name] stage | [Environment name] stage | [Environment name] stage |
Each stage in the workflow has its own status which indicates the progress status of the development in the entire lifecycle. The table below describes the workflow statuses in each main category:
Code Review Stage is optional
Testing is optional
This lets you to skip a stage when it is reached in the Lifecycle. This allows you to release to environments in the next phase without being required to deploy to any in the optional phase.What are the Internal issue's statuses?
While an issue moves through its lifecycle, the internal status of an issue indicates its current receives different In Agile.Now, there are internal statutes for while an issue is progressed describe the state of the task in the workflow progress. These statuses are built-in Agile.Now and appear as Issue's metadata on the Issue detail view.
An issue can be on one of the following states:
- Ready
- "Ready" status indicates that the issue is ready for an activity to be performed on it. For example, an issue in "To do- Code review" stage with an internal status "Ready" indicates that the issue is in the queue to be reviewed, whereas an issue in the "Done - Code review" stage with an internal status "Ready" indicates that the issue has been reviewed and is in the queue for moving to the next phase in the development.
- Review failed:
- This indicates that the issue was reviewed, however, it was not approved by the reviewer and therefore it is sent back to the developer.
- Review passed:
- This status indicates that the issue has passed the code review successfully and can be moved to the next step in the workflow.
- Test failed:
- Test passed:
- Deploying:
- Deployed:
- Deployment failed:
In order for an issue to move in the workflow, the user performs activities that change the status of issues