| Table of Contents |
|---|
This article describes how to move Jira tickets form status "Awaiting deployment" to "In bugfix review" depend on deployed service version on bugfest and version in Jira ticket.
Parameters
| Parameter | type | describe |
|---|---|---|
| BugfestEnv | list<string> | Bugfest environment: Nolana, Orchid, Pre-Orchid, Morning-Glory |
| Release | string | Name of Release that you are going to use. |
| JiraTaskStatus | string | Current status of jira task |
| NextJiraTaskStatus | string | Future status of jira task that you want to moved. |
| Comment | string | Comment for jira task after moved to next Jira status. |
Steps
- Go to Jenkins
- Navigate to Racher -> Automation -> Move-Jira-Tickets-depend-on-deployed-version-of-module
- Select parameters
- BugfestEnv - Select bugfest environment by default Nolana;
- Release - Name of Release you can find in Jira ticket in field "Release" by default "Nolana (R3 2022)";
- JiraTaskStatus - current status of Jira ticket can be founded in field "Status" in Jira tiket by default "Awaiting deployment";
- NextJiraTaskStatus - future status of Jira ticket can be founded trough "Workflow" in Jira ticket by default "In bugfix review";
- Comment - Comment that you want to leave after moved status task by default "Moved status to ${NextJiraTaskStatus} from status ${JiraTaskStatus}" (example how it looks "Moved status to In bugfix review from status Open");
- Click Build button;
- Wait for completion.
Job flow
Drawio border true diagramName Move Jira ticket depend on version modules simpleViewer false width links auto tbstyle top lbox true diagramWidth 991 revision 1
Example
