Atlassian Jira Plus is the system the development team uses to keep track of and communicate with each other about the projects they are working on. This article will cover checking on the status of a bug or feature request that you have submitted.
Note: For more information about how to use Atlassian Jira Plus to create or link issues, refer to the Bug Reporting Process Article or Feature Request Reporting Process Article.
Understanding the Jira Dashboard
To find the Jira Dashboard, navigate to https://corebridge.atlassian.net/
The Jira Dashboard is divided into different categories. Understanding their meanings can help you find the ticket and information you are looking for.
a. Issues in Backlog - Development is aware of these issues, but because they are not high priority, they are not being actively worked on at this time.
b. Issues in UX/UI Design - These issues have been selected for development, but the visual aspect needs to be determined before coding can begin. As such, they are being looked at by the design team.
Note: UX stands for 'User Experience' and UI stands for 'User Interface'.
c. Needs More Research or Information - These issues have been looked at by a project manager and are on-hold awaiting more information. Dev will typically reach out to the support agent if they are in need of more information from the customer or a replication in a system. However, if you are waiting on a ticket, it is a good practice to check this board to see if action is required from you.
Note: Dev uses several designations as to what information they are waiting on. When checking the status of your ticket, look for the designation Needs QA Replication. This means the development team needs information either from the support agent or from the Quality Assurance team.
d. Issues in Pre-Dev Prep - These tickets are in the first stages of development.
- PM Review: All tickets start by being reviewed.
- PM in Progress: Ticket has been assigned to a project manager.
- Ready for Dev: The ticket has been written up and selected for development. It will move to the next stage as a team becomes available to work on it.
e. Issues in Active Development - This is everything the development team is actively working on.
Note: The To Do designation means the ticket is on a board and waiting for a project manager to pick it up. All other statuses are various stages of in-progress.
f. Issues in Pre-Release Testing - This means the ticket is in the final stages of testing. Before being released, all tickets are put into a test system to monitor performance and look for issues.
- QA Testing: Anything marked as QA testing means it has already been tested twice and is very close to being released.
- Needs Fix on Release: an issue has been found and needs to be fixed.
- Release Fix in Progress: The issue detected is currently being worked on.
g. All Tickets Ready for Deployment - These tickets have been resolved and are ready to go out with the next release.
h. Training Priorities Recently Released in Last 7 Days - These are tickets that were submitted by the Training Team and have been released in the previous week.
i. All Recently Released Tickets in Last 7 Days - Any and all tickets that have been resolved and released in the last seven days. This is a great place to check for tickets you have been waiting on.
j. CSM Data Import and Changes - These are tickets that have been labeled as being associated with either an import or change to data.
- Import data refers to information coming over from another system. This can be either from another program or a customer moving from V2 to V3 and usually refers to customer and contact information.
- Data changes can refer to any kind of data issue caused by a bug. When this happens, dev will go into a system and change the effected information while waiting on the larger fix on the bug that caused the problem.
k. CSM Feature Requests - These tickets are ideas for new features that have been submitted by the CSMs. Many of these are on backlog. They are features that dev would like to implement, but haven't yet been able to allocate time for.
l. System and Franchise Reports and Widgets - Items submitted by the Training Team that have to do with reports and widgets.
m. Milestones - These dates are used to identify and organize tickets by priority. The milestone dates are the goal dates for release on the tickets. Please keep in mind, these dates are not guaranteed.
Note: The goal date is the first day of the month the ticket is listed under.
Understanding Symbols
Within these sections you will see many different symbols. These are located to the left of the END number. Understanding their meaning can provide insight into the tickets listed.
a. Task (Blue Checkmark) - This is a small item or fix such as adding a filter or changing a layout. Nothing is wrong with the current functionality, but a small adjustment is wanted to make it better.
b. Story (Green Ribbon) - This ticket will require some time to complete. It usually involves a major refinement on a feature or a brand new feature.
c. Epic (Purple Lightning) - This will require multiple stories to complete.
d. Bug (Red with White Circle) - Any submission that is a bug.
e. Issue Submission (Orange with and Exclamation Point) - Tickets for the Quality Assurance Team.
f. Data (Green with Horizontal Lines) - Any issue involving data such as an import. This goes to a separate team, not development.
g. Incident (Red with Lines) - QA uses this to designate important or high priority issues.
h. Priority Arrows - No arrow means normal priority. Yellow indicates a medium priority issue. Orange is high. Red arrows mean a ticket is urgent. If an issue is marked red, it becomes the main focus of the dev team until it is resolved.
Note: Tickets submitted by the Training Team are usually marked medium or higher.
i. Fix Versions - These numbers indicate the date that a task was completed. They are found in the sections listing tickets that are ready for release, or recently released.
Note: In this example, Ticket END-45671 was completed June 3, 2024. The number following the period refers to which release that day the task was finished.
Searching Jira
Begin by navigating to https://corebridge.atlassian.net/
1. Navigate to the V3 Customer Success dashboard located at the top of the screen. All tasks related to V3 will be found within this dashboard.
2. Select CTRL+F on your keyboard to bring up a screen search. As you type in the keyword or END number you are looking for, it will be highlighted on the page, allowing you to find and click on the project you are searching for.
If you are unable to find the project you are looking for in the screen search, use the search bar at the top of the screen.
3. Type the keywords or END number you are looking for in the search bar.
4 Use the Filter By Project to search for only those items in the Endor (V3) (END) category, allowing you to find and click on the project you are searching for.
2. Find and select your desired filter.
Note: You can utilize the search bar at the top to quickly locate the Filter you need.
3. Enter a subject or END number for the ticket you are searching for.
4. Select the ticket from the menu on the left to pull up the information.
Understanding Jira
Once you find and click on the project, it can be confusing to know what to look for. There are two main areas that will be most helpful. One is the Progress Bar at the top right of the page. This will tell you what stage development is in. ]The other area to look for is the Activity section near the bottom of the page. This allows you to see the progress development is making and what specific steps have been taken.
