NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Hi,
in our test environment based on JIRA 6.1 I try to implement some existing custom fields of my project into the customer portal.
If I a try to use an existing custom field (in create-screen available) it does not work.
If I create a new custom field (of type text or date picker) via administration it's not working.
If I create a new custom field (of type text or date picker) directly via an issue (new feature of 6.1) it works.
If I create a new custom field (of type lable) directly via an issue it's not working.
What's the rule behind this behaviour? Cannot find anything in our weak documentation (really unusual for Atlassian).
Cheers Sascha
- duplicates
-
JSDSERVER-86 Several custom field types can't be added to a request type
- Closed
-
- Gathering Interest
- relates to
-
JSDCLOUD-84 Implement existing custom fields in customer portal
-
- Closed
-
[JSDSERVER-84] Implement existing custom fields in customer portal
| Link | New: This issue duplicates JSDSERVER-7097 [ JSDSERVER-7097 ] |
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2305405 ] | New: JAC Bug Workflow v3 [ 3125859 ] |
| Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
| Workflow | Original: JSD Bug Workflow v5 [ 2059364 ] | New: JSD Bug Workflow v5 - TEMP [ 2305405 ] |
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2056791 ] | New: JSD Bug Workflow v5 [ 2059364 ] |
| Workflow | Original: JSD Bug Workflow v5 [ 1955319 ] | New: JSD Bug Workflow v5 - TEMP [ 2056791 ] |
| Workflow | Original: JSD Bug Workflow v4 [ 1614966 ] | New: JSD Bug Workflow v5 [ 1955319 ] |
| Description |
Original:
Hi,
in our test environment based on JIRA 6.1 I try to implement some existing custom fields of my project into the customer portal. If I a try to use an existing custom field (in create-screen available) it does not work. If I create a new custom field (of type text or date picker) via administration it's not working. If I create a new custom field (of type text or date picker) directly via an issue (new feature of 6.1) it works. If I create a new custom field (of type lable) directly via an issue it's not working. What's the rule behind this behaviour? Cannot find anything in our weak documentation (really unusual for Atlassian). Cheers Sascha |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-84]. {panel} Hi, in our test environment based on JIRA 6.1 I try to implement some existing custom fields of my project into the customer portal. If I a try to use an existing custom field (in create-screen available) it does not work. If I create a new custom field (of type text or date picker) via administration it's not working. If I create a new custom field (of type text or date picker) directly via an issue (new feature of 6.1) it works. If I create a new custom field (of type lable) directly via an issue it's not working. What's the rule behind this behaviour? Cannot find anything in our weak documentation (really unusual for Atlassian). Cheers Sascha |
| Link |
New:
This issue relates to |
| Workflow | Original: JSD Bug Workflow v2 [ 1602302 ] | New: JSD Bug Workflow v4 [ 1614966 ] |
| Workflow | Original: JSD Bug Workflow [ 1398358 ] | New: JSD Bug Workflow v2 [ 1602302 ] |