| Reporter |
Gaya Draznin (gaya)
|
|---|---|
| Created | Dec 24, 2012 11:11:15 AM |
| Updated | Mar 15, 2013 2:42:19 PM |
| Priority | Normal |
| Type | Usability Problem |
| State | Open |
| Assignee | Anna Zhdan (Anna.Zhdan) |
| Subsystem | Custom Fields |
| Fix versions | No Fix versions |
| Fixed in builds | No Fixed in build |
| Affected versions | No Affected versions |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Routine |
Hi,
We have number of projects, in each one involved different departments, like UX, R&D and QA, for example.
Each department need his own list of fields defined per task (for example, QA needs browsers list and severity, but other departments not).
According to this we cant use subsystems for departments.
Do you have any suggestions, how to structure YouTrack project for our needs?
Thanks,
Gaya Draznin
We have number of projects, in each one involved different departments, like UX, R&D and QA, for example.
Each department need his own list of fields defined per task (for example, QA needs browsers list and severity, but other departments not).
According to this we cant use subsystems for departments.
Do you have any suggestions, how to structure YouTrack project for our needs?
Thanks,
Gaya Draznin