Ability to set default issue labels per organization (colors and names)

[mehulkar]

It would be nice if each Organization could set a default set of labels for their issue lists. The default list provided by GH does not fit our needs and we do a large part of our project management via GH issues. Having consistency across projects would make it much easier to manage and schedule work, and also communicate progress to the rest of the team.

[stuartpb]

This could be done by an app, actually: I know waffle.io does it whenever I add a project to waffle.io/plushu/plushu (or at least whenever I drag a card for that project).

[mehulkar]

Yeah, probably. I'm sure there's an API for it. I think it would be a good feature for project management capabilities though.

[TPS]

#281 for orgs?

[iamerikjolson]

We use this shell script to delete the default GitHub labels and add our own. You can modify as needed for your purposes.
https://github.com/thisisarray/GitHub-Issues-Process/blob/master/set-github-labels.sh

[mordka]

In our organisation there are almost 100 repositories. Even when using waffle to automate adding labels, and git-labelmaker it's a daunting task to rename default and delete obsolete labels for each of the repositories.

[sypets]

Gitlab provides possibility to promote labels to "group labels". That way you have a set of group labels, but can also have specific labels for one repo.

GitHub does offer the "project" functionality by organization (as well as by repo). You can manage all organization-wide issues in projects. So, having a set of labels for an organization as well seems like the sensible next step to me.

[sypets]

I sent request to GitHub support about this and got answer:

Thank you for getting in touch with GitHub Support!

I believe adding support for Organisation level labels is something we'd like to implement. I'm not sure when we'll add this but we'll pass your feedback onto our Product Team consider.

[rosibaj]

Agree, agree, agree. consistency in labels is key for github project management across many teams at one org!

[iMazed]

Working in a team that has over 600 repos, I can only echo the need for this!

[coltenkrauter]

I agree

[clarkbw]

👋Hello!

I don't think this ask is going to get traction by itself.

I'm seeing a lot more asks for a system like #281 with the ability to have a central place for label standardization which would also act as the default set. The problem of org level labels is a larger scope problem but would have the effect of fixing this.

Wanted to make that known and perhaps it makes sense to merge this into the other.

[rosibaj]

I think org wide similar to this implementation is best: https://help.github.com/en/articles/creating-a-default-community-health-file-for-your-organization

Per repo creates a lot of extra work for managers

[mehulkar]

I can't remember now if I just opened the same issue twice or if I meant something different for each. Looks the same to me now. Closing this one i favor of the older issue. Please go 👍 that one!

[nunorafaelrocha]

@mehulkar care to share a link?

[dgw]

@nunorafaelrocha He's referring to #281 (comment).

[displague]

Here's yet another tool to take a labels.json file and create all of those labels against all of the repositories in your organization.
https://github.com/displague/github-labeller

I hope this helps!