fundamentals of jira for eed users november 2014

Fundamentals of JIRA for EED UsersNovember 2014

Why is this Happening?• ECHO Development Team has transitioned from Test Track Pro to JIRA for

Sprint Tracking and Agile Management• Better Planning and Tracking Tools• Value-add via Integration with other components• More accountability

What is JIRA• Issue Tracking Tool like Test Track Pro• Member of Atlassian Tool Suite• Wiki• Code Repository• Code Deployment Tools

• Used by• CMR• URS• Earthdata Search Client• GIBS• FIRMS• …

Where Can I Find JIRA?• URS Account and Access Privileges Required• For access, provide URS username via email to:

echo-ops@echo.nasa.gov • To View All Issues• https://bugs.earthdata.nasa.gov/issues/?jql=project%20%3D%20ECHO

How Do I Create Issues: Option 1• Test Track Pro is still available for creating issues!• Issues discussed and escalated as part of the PRB will be

escalated to JIRA instead of TTPro• Based on our research from the past 2 years, escalation is a

relatively seldom occurrence.• Escalation to JIRA will be done manually. Your name as the

reported, submitter site and comments/attachments will be preserved.

• This will continue to work for the foreseeable future.

How Do I Create Issues: Option 2

How Do I Create Issues: Option 2

1

2

How Do I Create Issues: Option 2

How Do I Create Issues: Option 2

3

4

5

Setting Security Level to “None” means that everyone will be able to see the issue you report.

How Do I Create Issues: Option 2

When the ECHO Review Board (ERB) evaluates new issues, it may request more information or adjust the priority level of the issue. As the reporter, you will automatically receive all updates on any issue you report.

How Do I Create Issues: Option 26

7

How Do I Create Issues: Option 2

8

9

How Do I Create Issues: Option 2

10

11

Adding Comments & Attachments

Bonus!

What is the PRB Process for Issue Escalation?• Minimal change to process

• Daily Reports • TTPro ECHO_TTs report continues• JIRA Report in place

• Escalated Tickets will be manually migrated

Issue Tracking with Filters

https://bugs.earthdata.nasa.gov/browse/ECHO-102?jql=project%20%3D%20ECHO

Advanced Tracking

Advanced Filter Building• Some Filters To Try• project = ECHO AND sprint = 10.86 AND component = Reverb• project = ECHO AND component = Catalog-Rest AND labels in (TTPro_Import)• project = ECHO AND reporter = cathyf

Keeping Track of Important Issues• Advanced Filtering Next Steps• Saving Filters• Sharing Filters

• Kanban Boards for Priority List Tracking

Keeping Track of Important Issues• Daily Subscriptions (Email us if you are not receiving these!)• Current Sprint Wiki Page (Email if you cannot see these)

https://wiki.earthdata.nasa.gov/display/UTC/ECHO+10.86

Verifying Issues

If you don’t see these options when trying to verify an issue contact us.

ECHO JIRA Workflow

https://bugs.earthdata.nasa.gov/secure/ShowConstantsHelp.jspa

Adding New Team Members• First Step: Ensure team member has URS account• Determine level of participation they desire/need• Daily Subscription Required?• Extra permissions?

• Email ECHO Operations: echo-ops@echo.nasa.gov

kbaynes

Where should I go with problems?

If you are having problems, there is potentially a configuration oversight on our

part. Reach out. We can help.

Email ECHO Operations: echo-ops@echo.nasa.gov