---
# System prepended metadata

title: Github and Gitlab Finalized Labels
tags: [V3.1 Organization]

---

# Github and Gitlab Finalized Labels

###### tags: `V3.1 Organization`

## New Final Labels

### Issue Status Labels:

#### Status: In progress

This issue is actively being worked on by an assigned member.

#### Status: Awaiting update

This issue requires another issue to be resolved first, or for someone to give a progress update. 

#### Status: Revisit

This issue will be revisited in the future!

#### Status: In review

This issue or merge request is being reviewed.



---

### Issue Lifecycle Stage Labels:

These labels are attached to issues to identify their current stage in an issue lifecycle. 

#### Stage: Inspection 

This issue was created by an external contributor and requires a team member to review it before it goes into the planning stage. 

#### Stage: Planning

This issue requires the team to analyze its details and complexity to prioritize it effectively.

#### Stage: Ready 

This issue has passed the planning stage, and is ready to be scheduled for a sprint.

#### Stage: Active

This issue is part of an active sprint.

#### Stage: Completed 

The team successfully completed this issue's tasks.

---

## Level labels

#### Level : Introductory 

This issue is suitable for anyone new to open source development.

#### Level : Regular

This issue is suitable for anyone who understands the basics of open source development. 

#### Level : Skilled

This issue is suitable for developers who are building their open source expertise. 

#### Level : Expert

This issue is suitable for developers with considerable open source expertise or for those looking for a good challenge. 


---

## Priority Labels

#### Priority: Low

This issue can wait, and can probably be picked up by anyone looking to contribute to the project.

#### Priority: Medium

This issue is useful, and needs some attention.
    
#### Priority: High

After critical issues are fixed, these should be dealt with before any further issues.

#### Priority: Critical

This should be dealt with ASAP. Not fixing this issue would be a serious error.


