What is the purpose of the issue type Implementation?

[Andrea Baker]

At our organisation we're attempting to consolidate our existing issue types for the purpose of simple and defined usage. One of the teams is using the issue type 'Implementation' as a sub task to group multiple Feature Releases or Production issues together so that nothing is missed on implementation. We're trying to justify removing this issue type as we'd like to ensure usage for all at scale in the enterprise however we're getting some push back from the team that is using this.

Our challlenge is that if we keep this issue type then all in the enterprise will have the option to use it and we're unclear of the value / best practice usage for this. 

Any advice/guidance on whether 'Implementation' issue type is something that should be scaled and if so then what is the defintion and descriptor for its best practice usage?

[Nic Brough -Adaptavist-]

The "best practice" for this issue type is whatever you need it to be.

Jira has "issue type schemes" which determine what issue types are available in each project, so you can have projects (and hence teams) with different uses of different types.

The value of it is not something we can tell you.  There's probably a good reason your team is pushing back against removing it - they find it useful.  You'll need to ask them how it is useful to them.  It could well be that they have a perfectly good reason, but no-one else works that way in your organisation - the best thing to do there is let them use it, but don't enable it in the other projects.