Content
Added by Franzi Moh over 9 years ago
Hi everyone,
I’m sorry, but I’ve got yet another question… (And I’m afraid there will even be more.) ;)
Is there a way to assign certain statuses to certain work package types only?
Example:
Possible statuses (available for selection in drop down list) for User Stories:
new / defined / in progress / waiting for QA / QA in progress / deployed
Possible statuses (available for selection in drop down list and used as column headers in Task Board) for Tasks:
new / in progress / done
Same question regarding other work package fields: Is it possible to enable/disable certain (standard!) fields depending on work package types? (For example it doesn’t make sense that someone can assign Story Points to a Task, but this field always exists for every work package.)
Can anyone help?
Best
Franzi
Replies (7)
Yes, we can :-)
Go to
Regards
Niels
Hi Niels,
well, I had come that far, but…
I just can’t see where I could define “show/assign this and that field to work package type AB and these other ones to work package XY (and hide all others in both cases)”. And in the Task Board always all defined statuses (for all work package types) are shown as columns.
Or am I missing something here?
Greets
Franzi
Okay, I think I found the solution to the status per type problem within the Workflow area (so that only Task statuses are shown in the Task Board).
But the question still remains if there’s a way to make sure that certain fields are only displayed for certain work package types (e. g. no Story Point field for Tasks).
In the Types setup, you can select the applicable custom fields for the type.
Yes, I know. But that’s only for custom fields (as you say). But what about the standard fields (the ones I didn’t create myself)? How can I remove them from certain work package types?
If I create a custom field “Story Points”, I have two “Story Points” fields, but am always just able to edit/manage the ones I created myself. I also added two custom fields “Start Date” and “Target Date”, but - again - then there’s two kinds of those fields…
Hello Franzi,
currently, you cannot (un
)select work package standard fields like you can (un)select custom fields. But I’d like to encourage you to write a feature request for this. :-)Kind regards,
Hagen
I’m interested in this as well: apparently there’s some sort of control on those fields under Administration > Settings > Work package tracking > Customize appearance. From there it looks like you can display or hide the fields, but nothing happens when checking the boxes. In any case, I’d like to take out the Assignee and Responsible fields out based on permissions: I intend to give clients a limited access to the platform to submit tasks and tickets, but don’t really want them to see my team composition and the developers assigned to that project. Certainly don’t want them to assign tasks to people either. I’ll review the submitted tasks and assign them myself.