What's the expected workflow?
1) CLECC assigns a set of 10 Jira tickets to volunteers (institution/individual) every 2 weeks.
2) Volunteer reviews Jira tickets. Expected work for 10 tickets is 3 - 4 hours total, over the 2 week period.
3) Put comments, notes, updates in status directly in Jira. Jira is the main communication device so we should make that the repository of findings.
4) Send note to CLECC on completion of the 10 issues. For each issue, include a one sentence description of the disposition. The next 10 issues will be assigned based on the clock (2 weeks), not based on completion of the 10 issues, unless requested. If the volunteer is not complete with the 10 issues after 2 weeks, reminders will be sent, but no new issues assigned.
Expectations
- Primarily this activity is a review and coordination activity, not a "doer" activity. That being said, if you find an issue that requires 20 - 30 minutes of work to complete, perhaps completing it will make sense, but that is optional.
- We are looking to have some movement on the tickets. That might mean getting clarification from the requester, closing the issue if the work is not going to get done, sending an email to the dev list to get opinions on the issue (which should end back up on the ticket), bringing up on the CLE Release team call, assigning the issue to the appropriate person, and changing Jira fields to reflect actual current status.
The Jira Triage working group meets weekly to review newly created Jira tickets for Sakai.
Newly created Jira tickets are in an "awaiting review" status. The Jira Triage group reviews these tickets weekly to ensure that the ticket contains all required information for the developers to begin working.
The Triage team will help ensure that:
- The ticket summary is clear and matches the issue.
- A test plan is provided when needed, and the test plan contains the clear steps to identify if/when this issue is resolved.
- The ticket priority is set according to Sakai community policies
- Components are listed.
- The affected versions are listed.
- Any appropriate labels are applied to flag this issue for other working groups (ie Accessibility, Teaching & Learning, UX)
After review, the ticket status is updated.
- Open: Ticket has been reviewed and is ready to be worked on or discussed by other working groups as needed.
- Awaiting Information: The ticket is missing key information, such as affected versions, test plan, or key details. The ticket can be opened once this information is provided.
- Closed - Duplicate: The ticket duplicates an existing Jira ticket. The duplicate ticket will be linked.