-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
None
-
1
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Problem Definition
Ability to create multiple unique forms under an individual issue/request type
Suggested Solution
Customer can continue to create individual request types, but if they have a requirement to have 20-30 unique forms then customer is going to have 20-30 unique issue/request types which of course would become unmanageable over time.
Why this is important
It would be incredibly useful to have the ability to create multiple unique forms under an individual issue/request type so that you can capture the right information at the first point of contact from the customer. The best example for this would be Service Requests as they can come in all different flavors.
Possible Service Requests that would need a unique form are as follows:
- New employee request form
- Employee leaving form
- Database access request form
- Hardware ordering form
- Software ordering form
- Basically anything that either needs to be approved or tracked.
Workaround
No
- relates to
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-4643] Ability to create multiple unique forms under an individual issue/request type
| Resolution | Original: Won't Do [ 10000 ] | New: Low Engagement [ 10300 ] |
| Status | Original: Closed [ 6 ] | New: Closed [ 6 ] |
| Resolution | New: Won't Do [ 10000 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Workflow | Original: JAC Suggestion Workflow [ 3012557 ] | New: JAC Suggestion Workflow 3 [ 3647455 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2663880 ] | New: JAC Suggestion Workflow [ 3012557 ] |
| Support reference count | New: 1 |
| Workflow | Original: JSD Suggestion Workflow - TEMP [ 2322503 ] | New: Confluence Workflow - Public Facing v4 [ 2663880 ] |
| Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
| Workflow | Original: JSD Suggestion Workflow [ 2053999 ] | New: JSD Suggestion Workflow - TEMP [ 2322503 ] |
| Workflow | Original: JSD Suggestion Workflow - TEMP [ 2049302 ] | New: JSD Suggestion Workflow [ 2053999 ] |
| Workflow | Original: JSD Suggestion Workflow [ 1637025 ] | New: JSD Suggestion Workflow - TEMP [ 2049302 ] |
| Description |
Original:
h3. Problem Definition
Ability to create multiple unique forms under an individual issue/request type h3. Suggested Solution Customer can continue to create individual request types, but if they have a requirement to have 20-30 unique forms then customer is going to have 20-30 unique issue/request types which of course would become unmanageable over time. h3. Why this is important It would be incredibly useful to have the ability to create multiple unique forms under an individual issue/request type so that you can capture the right information at the first point of contact from the customer. The best example for this would be Service Requests as they can come in all different flavors. Possible Service Requests that would need a unique form are as follows: * New employee request form * Employee leaving form * Database access request form * Hardware ordering form * Software ordering form * Basically anything that either needs to be approved or tracked. h3. Workaround No |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-4643]. {panel} h3. Problem Definition Ability to create multiple unique forms under an individual issue/request type h3. Suggested Solution Customer can continue to create individual request types, but if they have a requirement to have 20-30 unique forms then customer is going to have 20-30 unique issue/request types which of course would become unmanageable over time. h3. Why this is important It would be incredibly useful to have the ability to create multiple unique forms under an individual issue/request type so that you can capture the right information at the first point of contact from the customer. The best example for this would be Service Requests as they can come in all different flavors. Possible Service Requests that would need a unique form are as follows: * New employee request form * Employee leaving form * Database access request form * Hardware ordering form * Software ordering form * Basically anything that either needs to be approved or tracked. h3. Workaround No |