JIRA

•The Why of JIRA - Reasoning for the migration

The previous JIRA was created to align to with the stages of the project lifecycle. Items for remediation, solution requests, GPO approvals, project activities, documentation and quality reviews were scattered throughout many different JIRA projects making it extremely difficult to gauge the status and health of each deployment project.After a review of this problem a new JIRA was proposed which combines all aspects of a deployment  project into one JIRA location. There is an integrated workflow process which takes an issue from the remediation process all the way to the system integration process in preparation for go-live.From mid-September to late-October the deployment teams worked to identify and gather all JIRA issues related to their respective projects and uploaded this information into the blue JIRA instance. After the migration the teams went through the issues to sanitize the issues further and begin to assign those to the appropriate individuals or functional areas, i.e., Soulution Architects, GPOs, Development Team, etc.Direction was given to the GPOs and Solution Architects that they should use deployment projects only and review and approve the issues in those projects in order to improve the management of  the solution requests.The existing COEGTG, GTWINF, DEPLAPRM, DEPLAMX and DEPLABR green JIRA projects should not be used for any deployment project activities.

•The Where of JIRA – URLs for team members

•

•The When of JIRA – Timeline

•The How of JIRA – Functionality differences

•

•The What of JIRA - Using JIRA, searching, filtering, dashboards

•

•The expectations from all Users, issue creation and timekeeping

•Dashboards to provide “at a glance” information, standard or custom,Issue creation, assignment, approval and closure,Project reporting information provided in workbooks or charts. 

Time tracking, individual or by teams

•

• Orderly process workflows which follow development lifecycle

•

• Issue escalation and review

•

• Search for issues across projects or filter and focus on specific details