Team Central: Is it possible to remove a label that was created accidentally or incorrectly

Question

As we are starting to circle around how we would like to implement this product, we realized that we have some labels that we don't want to use.

To prevent confusion, is it possible to remove labels that we have created?

The look up is an exact lookup, so if I have test-label, and type label, test-label does not appear - so someone might make label-test as a duplicate.

When we find that we will want to clean it up so that we are driving consistency.

Leah Picone_360ci9 · Answer

Hi @Sherif Mansour

That's what we are trying to determine. Understanding that clicking on the label actually presents a label dashboard was very helpful.

Knowing that this is a product in development, I am trying to control my enthusiasm for adding features. But since you asked :)

* Why pre-create labels?* Mostly because I would like to control the confusion that incorrectly created, labeled items cause. We can establish the hierarchy and define how others should use it.
* Our roadmaps have:* Work Tracks: high-level themes:* Platform Services (ie: standardized enabling services used by all products)

* Work Subtracks: mid-level themes:* Org Services (authentication protocols)

* Theme: Program * Org / Identity

* Capability:* Data Standardization
* Licensing and Provisioning
* Platform Maintenance

* Feature:* Upgrade integration for new SalesForce version (Let's say this is for Data Standardization)

I imagine at any point in time, someone will want to see how the progress is being made at any of the bold items. Based on the current functionality we are thinking that we would do:

* Feature = Projects
* Capability = Label
* Theme = different Label (not Capability)

We were looking at how we might be able to use Goals to do some level of this also, but I think that I am starting to move way from that thinking.

I am pondering if I have the desire for any type of prioritization values of projects also, but we are still working through the thinking. We are creating Projects in Pending status as we ramp up, and it might be helpful to understand when they should start, as we are only able to say when they should end.

Sherif Mansour · Answer

What kinds of things does labels you want to pre-create represent, @leah ? is departments? themes? programs?

Just trying to better understand the context as we might be working on some features that could help this in the longer term - we're trying to pull in org hierarchy to make it easier to create, connect with and report on projects and goals and I'm unsure in your scenario is labels being used to represent this?

MA_ubx03t · Answer

Depending on your appetite for custom fields, the number of the set of labels that you want and how strictly you want to govern them, you can create a custom field with a set pick list of valid values.  We use these for managing risk through a preset list of options for risk likelihood and risk consequence.  The inbuilt labels are effectively a tag and are visible across all projects.  This can be a bit annoying if different labels are relevant to different projects.

Good luck with finding a suitable solution.