Tl;dr
Jira
- Add Add a closing comment with details such as confirmation from customer date/time (optional: attach email from customer, giving the confirmation),
- Complete Stash steps and Move the ticket over to the "DONE" column
Stash
- For For new projectprojects:
- Create a new
- repository in FNF project
- Clone to local
- Add the nitro file from TEST environment
- Commit and push to master (from local to remote),
- When committing, include the Jira ticket, by using a string "JIRA <TICKET>" (example: "JIRA FEB-530")
- For For existing projectprojects: do the above, except for the first part of creating a new repository
- Do the Steps 2 - 4, above
Confluence
Update the project requirements page, under the FEB space
...
:
- For new projects:
- Update the Document Properties box:
- "Document Status" at the top and other sections (such as Pre Go-Live, etc,) as necessary
- Update the Document Properties box:
- For existing projects:
- Update the "Post Production Enhancement List" section
- "Description" to capture enhancement(s) at high-level; provide a link: if you have a detailed documentation page (where this set of enhancements are captured in detail)
- After receiving confirmation/notification for Stash step #18 (that the tag has been deployed in PROD)
- Update Version (in PROD) property (Document Properties box) with the latest version
- Update the "Post Production Enhancement List" section
...
Jira
Update the ticket
- Provide Provide the following details in comments: Who approved the go-live and when.
- If possible If possible/you'd like to, attach the email confirmation to the comments
- AFTER completing the Stash steps: Move the ticket from "UNDER REVIEW" to "DONE" column; ensure that the ticket's workflow status is "DONE" and not "CANCELLED"
- Notify Jason Card that the "Tag" has been created (Stash step #18)
Stash
Brand New Project | Existing Project |
---|---|
| Start from step 5, on the left. |
...