Our current set up uses a project and multiple teams have their own boards which is filtered down by components (e.g. each team owns multiple components so the board filter captures said components).
One of my team wants to stop using the estimates fields and use a custom 'T-shirt size' field.
Is it possible to remove the estimates field for this team without removing it across the project impacting other teams?
I assume I'd need the t shirt size team to have their own workflows or screen schemes but I'm not sure exactly what I should be making for what purpose?
If anyone has done this I'm eager to hear how it worked or if there are any better solutions?
Thank you :)
Welcome to the community @Indya Kachela !
A workaround would be that this team has its own issue type. For this issue type, you would use a different screen that doesn't have the Estimate field instead having the custom field. Different workflow is not necessary, rather the issue type scheme with the issue type screen scheme. And yes, they would need a different screen scheme where you would use your screen with a defined new custom field.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.