Ticket Taxonomy

Ticket Taxonomy

We have defined an issue ticket format that has to be leveraged by organisations. This is where you can access the format.

It contains the following details.

Ticket Details:

• Title: Concise name for the project.
• Description: An explanation of the project, including goals and the problem it seeks to address.
• Expected Outcomes: A clear list of what the finished project should achieve.
• Acceptance Criteria: Conditions that the contributor must meet for the PR to be merged
• Mockups & Wireframes: Any relevant mockups for reference of the contributor if required.

MetaData:

• Project Name: Name of the project as defined by mentor
• Organization Name: The name of the organization proposing the project.
• Domain: The area of governance the project pertains to (ex: agri, healthcare, ed etc).
• Tech Skills Needed: Specific technologies, languages, or skills needed to complete the project.
• Mentor(s): The names of any assigned mentor(s) from the organization.
• Complexity - An estimation of the project's complexity - High, Medium, or Low.
• Category of project - We have defined multiple types of projects (ex: integrations, bug fixing etc) & basis the nature of the ticket you can choose one of the types.
• Sub-Category- Please add a sub-category basis for the examples mentioned in the issue template.