-
Suggestion
-
Resolution: Duplicate
-
None
-
application server
I manage 12+ projects for the Engineering group. The workflow for all projects is identical (to save my sanity). They share all the same fields, schemes, etc. The versions and Components are not. I would like to be able to say that a workflow, screen scheme, permission scheme, field scheme belongs to a Project Category so that I can add a new project more easily and have all custom fields, screens, workflows, permissions available to the new project. Fisheye/perforce integrations would be simpler if Project Category were available there also.
- duplicates
-
JRASERVER-67231 Allow support for project schemes or templates
- Closed
-
JRASERVER-7020 Allow support for project schemes or templates
- Future Consideration
[JRASERVER-23247] Use Project Category to configure the project
Workflow | Original: JAC Suggestion Workflow [ 3047154 ] | New: JAC Suggestion Workflow 3 [ 3672700 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2606334 ] | New: JAC Suggestion Workflow [ 3047154 ] |
Link |
New:
This issue duplicates |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2557599 ] | New: Confluence Workflow - Public Facing v4 [ 2606334 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2342311 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2557599 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2123568 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2342311 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2085525 ] | New: JIRA Bug Workflow w Kanban v6 [ 2123568 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 886478 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2085525 ] |
Labels | New: affects-server |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 713595 ] | New: JIRA Bug Workflow w Kanban v6 [ 886478 ] |