Feature Request: Adding customized issue labels for talawa suite #648

[SiddheshKukade]

Is your feature request related to a problem? Please describe.
As the contributors to the talawa projects are increasing drastically year after year there are a lot of changes that are being added, changes or fixed everyday. Having some customized issues labels for our talawa apps and APIs would be great to links issues together and track them as parent of children of each other

Describe the solution you'd like
I'd like to extend the issue labels with the following:

For Talawa-docs

technical: adding docs related to the technicalities of the talawa apps.
user-guides: for adding docs related to onboarding new users, explaining new concepts in a non technical way,etc.
design: realted to the design of the docs website
misc: for other miscellaneous issues

For Talawa-admin, API and Mobile

COLORED IN LIGHTGRAY
parent: The issue is generating more sub-issues
children: The issue which is generated due to other parent issue.

COLORED IN YELLOW
figma: issue related and being worked with the figma file of the Admin UI

ALL COLRED IN PURPLE
area/performance: related to improving performance of website
area/ci-cd: relted to CI/CD workflow
area/tests: related to adding tests
area/ux: relted to UX improvements

USED TO LINK ISSUES ACROSS REPOS

for ex. if a problem from api causes issues in admin

component/api: Issues related to the talawa API
component/admin: Issues related to the talawa Admin
component/mobile: Issues related to the talawa mobile

ALL COLORED IN WHITE

issue/blocked: blocked due to another pending problem.
issue/design-required: Design template is require before proceeding
issue/blocked: remind tag to check issue in the future time (basically means issue is not relevant right now)
issue/stale: problem desribed is stale or outdated.

PR labels:

ALL COLORED IN LIGHT BLUE
pr/do-not-merge: Can't merge due to merge-conflicts of files or a important review is required.
pr/on-hold: if the linked issues is on hold
pr/dependancies: related to adding dependancies in the project

Describe alternatives you've considered
Please suggest alternatives in comments

Approach to be followed (optional)
IMPORTANT: Someone with a member access to the Palisadoes Foundation is required to add the issue lables in each repo with the description

[SiddheshKukade]

Feel free to add comments and suggestions below 😃

[SiddheshKukade]

I've referred these labels from various other open source mobile, web and API projects

[palisadoes]

Closing. Let us know whether it should be reopened.

[SiddheshKukade]

This is completed this section will serve as a guide to show the details behind label abbreviations.