Provide support for ticket creation so that SMEs (anyone) can share needs and development projects with the community in a consistent way
introduce a process to maintain Jira so that we have a clearer and more current picture of needs and development activity throughout the community
establish guidelines and lifecycle process for ticket management in order to improve overall quality of tickets (improve reporting, navigation, communication, reduce duplicative effort)
Assumptions
Improving comfort level with Jira is a dependency for rolling out SIG prioritization
Impacts:
Conveners
POs
Some groups do not have assistant POs, so SMEs may need to create tickets in certain situations
Tickets need to be created earlier in the process
Permission
Who should have which permission sets
sometimes Jennifer creates a ticket but a PO has to clean it up
Need clarification re Where do you create the ticket?
How do we address cleanup / maintenance
Backlog - how do we manage the backlog
What is the process for assigning?
Could we allow SMEs to create tickets but then assign to PO for completion / vetting
How does this intersect with Support SIG - should they be responsible for Jira oversight? Should these be separate pipelines or combined
using project language
What is Needed
Process documentation - who creates tickets, how do they move through
Guidelines - POs are working on this, can PC provide input?
Jira training
Creating tickets
creating filters + dashboards
searching / navigating
Documentation
Ticket elements (required elements, templates, data dictionaries)