Custom Task ID at the Workspace, Folder, List level, subtask
Rich Manzana
Current this is only available at the space level. I'd like create Custom Task IDs at all levels. Workspace, space, folder, list.
Log In
Saskia Mardi
Yes please - currently I need so many spaces to be able to have different custom task ids. Also the ability to rest numbering of the custom task ID would be great.
Joanna Cendrowski
We would love this at the folder level at least. It'd be a game changer! We have Spaces FOR ALL our clients because we need the custom task IDs to be client-specific (for Github and Harvest time tracking). But would love a space for out Support clients, where each folder is a different support client. It would allow us an easy view of ALL active tickets in Support.
Nhel Rosal
Upvote - We currently need this in our project this help allot for setting up transaction No. and Membership ID in the same space
Collin Bentley
Upvote — very desirable functionality at least at the list level, as well as ability to define Custom Task IDs for different types of tasks (custom defined tasks) within a space. For example, Incident task type should have the INC-123 custom ID, while Change task types should have CHG-123 custom ID.
A
Adrian Berca
Upvote
S
Sarah Humphries
This is a must have for us to be able to create at list level
A
Alan
Sub-tasks should definitely be able to be suppressed from the main task custom task ID so it shows nothing, or e.g if “1” is the main task number, the sub-task should have a level e.g. 1.1. This will preserve continuous numbering at the task level which you should also be able to sort and filter with. It’s essential for managing a ticket based system of any kind that needs a unique reference without being on all sub-tasks.
L
Leonardo Turra
I agree! I'm particularly interested at Custom Task IDs at the list level.
Joanna Cendrowski
Yes, I need Custom Task IDs at folder level too!! It's a nightmare at the space level for agency work.
Why... we are an agency where every client has to have their own space, because we rename the task IDs with the client's acronym so when the task ID gets printed in Harvest and Github, we can ensure it is the correct client easily. Right now each client has their own space, which is nightmarish for our engineers to have a wholistic view of the tasks on their plate. Ideally we'd have a space for Discovery, Design, Builds, Support, so teammates can look at the space level at the tasks assigned to them (or that need their review). But now that every client is their own Space, it's hard to get an overview of the tasks they should be working on or watching the progress on.
Nicole Dupont
I agree! I'm particularly interested at Custom Task IDs at the list level.
Load More
→