Tl;dr

Jira

•  Add  For New or Existing Projects
  1.  Create a ticket for the project / requested changes for a project
  2.  Move ticket from "Backlog" to "In Progress" workflow stage
  3.  When done, notify customer / Move ticket to "Under Review"
  4.  Log work & 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 new projects
  1. pertinent details (e.g. go-live approved by name/date/time etc.)

Stash

•  For New Projects:
  1.  Create a new repository in FNF project
  2.  Clone repository to local (using Sourcetree)
  3.  Add the nitro file from Leap TEST environment
  4.  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 existing projects: Do the Steps 2 - 4
  1. branch,
  2.  Create a tag and notify Jason Card  for it to be released to PROD

•  For Existing Projects:
  •  Do Steps 3 - 5, above

Confluence

...

•  For New Projects:
  1.  Add a project requirements page

...

•  For new projects: Update
  2.  Add all the pertinent information related to this project
  3.  When ready to go live, update the Document Properties box
  : "Document Status" at the top and
  1. and and any other sections
  (such
  1. as
  Pre Go-Live, etc,) as
  1. necessary
•  For existing projectsExisting Projects:
  1.  Update the project's requirements page
     1.  Update the "Post Production Enhancement List" section
  2.  
  "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

Jira

Update the ticket

1.  Provide the following details in comments: Who approved the go-live and when.
   1.  If possible/you'd like to, attach the email confirmation to the comments
2.  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"
3. Notify Jason Card that the "Tag" has been created (Stash step #18)

Stash

...

• 1. After the changes have gone live:
     1.  Add release date to the "Post Production Enhancement List" section

Customer Notification

•  For New or Existing Projects: 
  1.  Copy links for Form(s) and View Responses page from Leap PROD environment
  2.  Notify customer/team that the latest changes have gone live and provide the links

...

Jira

For New or Existing Projects

Step #	Description
1	If new project:  Create a ticket in Jira for the project if one does not exist If existing project:  Create a ticket in Jira for the requested changes to a project
2	(Optional) Log the estimated effort
3	If the ticket is in the "Backlog", move it to "In Progress" when you start working on the changes
4	(Optional) If existing project: Link to the Project's parent ticket (v1.0) and provide a comment as to why you are linking to it... Info title FYI I usually do a "relates to" linking between Parent and post go-live enhancements Image Added Image Added Image Added
5	(Optional) As you progress, through the requested change(s)— a. Add comments as necessary b. Log work / time spent Image Added Image Added Image Added
6	(Optional) If scope change occurs (i.e. additional changes are requested by the customer), you may create a Smart Checklist. Markdown syntax is used for adding items and it is pretty simple and straight-forward. Info title Note Normally, the proper way to handle scope change would be to create sub-tasks — i.e. child tickets. However, for FEB tickets it has been recommended to not do sub-tasks (as it "messes-up" (or was it "fudges" Image Added) the reporting of Michael Oatley ) Image Added
7	When all requested changes are complete, notify customer and move the ticket into "Under Review" workflow stage Image Added
8	Upon receiving confirmation from the customer that all changes have been tested, verified, and confirmed, provide the following details in comments: a. Who approved the go-live and when. i. (Optional) Attach the confirmation email from customer to the comments b. Log work / time spent

Stash

•  Brand New Project

•  Existing Project

Brand New Project

...

Clone Add 2 ---- this folder 2Sourcetree will notice the and list it
Image Removed

Select either "Stage All" or "Stage Selected", depending on your circumstance

Under comments, follow the following format (without quotes):
"JIRA XXX-###
YOUR COMMENTS"
" (where XXX is the project key, in Jira and ### is the ticket numberNext, create a tag, by clicking

Next, make sure you select the "Push changes immediately to..." checkbox

Finally, hit the "Commit" button.

Example of Steps 9 - 11:

Image Removed

Image Removed blue line Give it an appropriate name; generally, Image Removed (Image RemovedNotify that the tag

Step #	Description
1	Login to stash: https://stash.uconn.edu/
2	Navigate to FEB Nitro Files (FNF) project
3	Provided you have the necessary privileges, click on the "Create repository" button, top-right Image Modified
4	Provide an appropriate name and then click on the "Create repository" button Image Modified
5	Clone repository to local — this is your local repository Tip title Tip Establish clean directory structure for all your Leap apps; directory within this structure is where you will create a local repository  a. Create a project directory for this Leap application b. Use git/bash command: Make sure you are inside the project folder of where you want to clone and then execute the following command: Code Block language bash theme RDark title Clone Remote Repository linenumbers true git clone REPOSITORY_URL Image Modified
6	Open up Sourcetree software
7	Add a new repository, by clicking on the "+" at the top: Image Modified a. Click on Add at the top: Image Modified b. Click on "Browse" Image Modified c. Navigate to where you cloned locally (Step	5.a., above) d. And click on "Select Folder"	— DO NOT click on the .git folder... merely ensure that the folder you select has a .git folder (this is a hidden folder — so you might not see it, based on your settings), as shown below Image Modified e. Finally, click "Add" Image Modified Anchor Continue from here Continue from here
8	Go to Leap TEST environment and export the project (if you have not done it already) and save it locally Info title Heads-up! Unless you have been told otherwise: Make sure that the "Include submission data?" checkbox is  not checked!
9	Locate the *.nitro_s file that you downloaded from Leap TEST environment and move it to	the directory of your project's local repository (same folder as	5.a., above)
10	Sourcetree automatically detects a change in	your local repository	; it's time to stage your project's nitro file — Reference the screenshot below for steps 10.a & 10.b: a. Your project's nitro file will be listed under "Unstaged files" section	b. Click on Image Added Image Added Info title Note: You should only see your project's nitro file... if you see more than one file, reach out to our Leap group and troubleshoot as to why that is the case
11	Select "File Status" tab (if it is not selected) Image Added
12	Committing to remote repository — Reference the screenshot below for steps 12.a — 12.c:   Image Added a. Under comments, use the following format — the first comment line & its format is mandatory! Code Block language text theme RDark linenumbers true JIRA XXX-### YOUR COMMENTS (where XXX-### is the Jira ticket; you can provide your comments after that)	Tip title Tip If you have a prior commit, you may click on the Image Added icon and select an applicable comment. If you select a comment from history, be sure to change the ticket number (and the comment, if applicable)! b. Click on Image Added c. Click on the Image Added button
13	Create a tag  a. Click on "master" under "BRANCHES" on the left; notice that middle pane	Image Added  b. Right-click on the	commit that you did in (Step 12, above) and select "Tag..."		Image Added c. In the resulting dialog box, under "Add Tag" tab i. Provide a name for the tag (this convention should work: "NAME_OF_REPO_v#.#"	, where #.# is your version number e.g. 1.0, 1.1, etc.)	ii. Select/check the Image Added checkbox iii. Click the Image Added button Image Added
14	Notify Jason Card that the tag "TAG_NAME" (from #13.c.i) has been created and it's ready to go live.	Start from step 5, on the left.

Confluence

Existing Project

Confluence

For a Project's Initial Release

...

...

...

Log Go-Live Date Date of Last Deploy in TEST Customer/Designee Sign-off & Date/Time Version Developer JIRA Ticket Release to PROD Date/Time Released By @DEVELOPER NAME  JavaScript files: using minified versions?  Confirm Security/Access Control (as reflected on THIS page)  Update Jira Ticket  Stash component  Queued for Go-Live! / Notify Jason Card  Update project's requirements page on Confluence  Notify customer/team post deployment with relevant link(s)
2	Follow/go through the developer's checklist, as listed within the Pre Go-Live Log
3	Update the  Document Properties  box "Document Status" should state  Status colour Blue title PRODUCTION
4	If you have done detailed documentation for your project, add a link to it right after the Document Properties box by: a. Adding an Info macro, with the following verbiage This is a high-level requirements document ONLY. If you are maintaining this application, are performing a maintenance, or just interested in the details, please reference the detailed documentation. b. Format the text as: Heading 2 c. Add a link back to the high-level requirements document on your detailed documentation page, with the following verbiage This is a detailed documentation for this project. If you would like to get a birds-eye view (Tl;dr) version, please reference the high-level documentation. d. Optional: if you have Table of Contents (ToC) macro on either the Detailed Documentation page or the High-Level Requirements Document page, edit the ToC macro and add the following RegEx so that it is excluded from it: Code Block language text theme RDark This is a detailed.* High-Level Requirements Page Detailed Documentation Page Image Added Image Added
5	Update any other details as necessary
6	Verify & confirm the accuracy of: User Interaction & Design Diagram Security / Access Control

For a Project's Subsequent Releases

Customer Notification