-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Problem Definition
Currently is only possible to create JIRA Issues from Confluence if JIRA has only these fields as required:
- System fields:
- Component
- Fix Versions
- Affect Versions
- Priority
- Due date
- Environment
- Assignee
- Reporter
- Labels
- Custom fields which have these field types such textfield, textarea, URL, number
Some customers need different field types to be required, which prevents this functionality from working.
Suggested Solution
As a Confluence and JIRA user, I would like to be able to add different custom fields (' types) as required. Ideally, I'd like to be able to add any custom field I have in my JIRA instance as required, and this field be recognised in Confluence during the issue creation.
- duplicates
-
CONFSERVER-31867 Ability to map more fields from a Confluence table into a Jira issue when highlighting and creating issues
- Not Being Considered
- relates to
-
CONFCLOUD-38073 Ability to create issues with required custom fields that aren't default field types
- Closed
[CONFSERVER-38073] Ability to create issues with required custom fields that aren't default field types
Workflow | Original: JAC Suggestion Workflow 4 [ 3571645 ] | New: JAC Suggestion Workflow 3 [ 4339672 ] |
Workflow | Original: JAC Suggestion Workflow 2 [ 3178308 ] | New: JAC Suggestion Workflow 4 [ 3571645 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3037356 ] | New: JAC Suggestion Workflow 2 [ 3178308 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2531629 ] | New: JAC Suggestion Workflow [ 3037356 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 2279194 ] | New: Confluence Workflow - Public Facing v4 [ 2531629 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 - TEMP [ 2160262 ] | New: Confluence Workflow - Public Facing v3 [ 2279194 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 1920150 ] | New: Confluence Workflow - Public Facing v3 - TEMP [ 2160262 ] |
Workflow | Original: Confluence Workflow - Public Facing v2 [ 1753151 ] | New: Confluence Workflow - Public Facing v3 [ 1920150 ] |
Description |
Original:
h3. Problem Definition
Currently is only possible to create JIRA Issues from Confluence if JIRA has only these fields as required: * System fields: ** Component ** Fix Versions ** Affect Versions ** Priority ** Due date ** Environment ** Assignee ** Reporter ** Labels * Custom fields which have these field types such textfield, textarea, URL, number Some customers need different field types to be required, which prevents this functionality from working. h3. Suggested Solution As a Confluence and JIRA user, I would like to be able to add different custom fields (' types) as required. Ideally, I'd like to be able to add any custom field I have in my JIRA instance as required, and this field be recognised in Confluence during the issue creation. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-38073]. {panel} h3. Problem Definition Currently is only possible to create JIRA Issues from Confluence if JIRA has only these fields as required: * System fields: ** Component ** Fix Versions ** Affect Versions ** Priority ** Due date ** Environment ** Assignee ** Reporter ** Labels * Custom fields which have these field types such textfield, textarea, URL, number Some customers need different field types to be required, which prevents this functionality from working. h3. Suggested Solution As a Confluence and JIRA user, I would like to be able to add different custom fields (' types) as required. Ideally, I'd like to be able to add any custom field I have in my JIRA instance as required, and this field be recognised in Confluence during the issue creation. |
Link |
New:
This issue relates to |