Our company run a number of projects that follow different processes. It would be good if some of the list fields could be defined at a project level. e.g.:
* Priority
* Status
* Risk
* Type
by: Ross M. | over a year ago | Administration
Completed
I would like the ability to have different list items for different projects
by: Ross M. | over a year ago | Administration
Copyright © 2025, Digital.ai Software, Inc. All Rights Reserved
Comments
I could see the value in setting different statuses (to match the Kanban/Scrum Board for each team) at the project level. This makes sense only in a large enterprise environment though... small companies like mine should try to standardize.
Voting for it to support environments like my prior employer.
Small companies (mine is < 100 employees) with varied projects have the same problem.
This idea is related, but broader: https://ideaspace.versionone.com/default/Idea/Detail/140
It would be good if some of the list field VALUEs could be defined at a project level. Perhaps that's what Ross meant? For example, I need 2 backlog item Types (Enhancement/Feature) for one project but I need 6 different backlog item Types (TSR, Template Change, Script, Content Request, etc.) for another project. I have a small company (<50 employees; 20-something V1 users) with two radically different types of work, types of skill, types of process, types of product. This isn't just a large company thing.
One might also word this item like this:
project level customizations for the built-in list type values