-
Bug
-
Resolution: Duplicate
-
Medium
-
None
-
4.2.13, 4.3.7, 5.1.2
-
- Confluence 4.2.13
- Jira 5.2.2
- Greenhopper 6.1.0
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Atlassian edit
If you use the insert JIRA Issue Macro to create an issue on a confluence page, it only takes the default required fields into account. If you have defined any other fields in your field configuration to be a required field, it will not show up in the macro. When trying to create the issue, the error message as described above will appear.
Original report
We have the following setup:
- Confluence 4.2.13
- Jira 5.2.2
- Greenhopper 6.1.0
Confluence and Jira are trusted applications.
When we try to create a new epic via the Jira-Issues-Macro we get the following error message:
There were errors creating an issue in JIRA. Some required fields may not be available on this form. Try creating this issue in JIRA
- customfield_10301: Epic Name is required
- Epic Name is required.
With all other issue-types this works perfectly.
Now we discovered, that the field "Epic Name" is a custom-field from Greenhopper and is mandatory. But with the Jira-Issue-Macro you cannot create Issues with customized mandatory fields. Now, the point is that we have not customized the field "Epic-Name", this comes form the Greenhopper installation. And Greenhopper needs an value in this field to work properly.
The feature to be able to create JIRA-Issues out of Confluence is very important for our business-process and furthermore it would be nice if you can define mandatory fields as you like and they appear in Confluence in the Jira-Issue-Macro-Wizard.
Are there any workarounds for this bug?
greetings
Benjamin
- duplicates
-
CONFSERVER-23424 The form provided when creating new issue with JIRA Issues macro should provide a form that contains basic fields required for the particular project chosen
- Closed
- relates to
-
-
- Closed
-
- mentioned in
-
Page Failed to load
[CONFSERVER-27825] Error when trying to create an Issue via Jira-Issues-Macro (required fields)
| Workflow | Original: JAC Bug Workflow v3 [ 2894784 ] | New: CONFSERVER Bug Workflow v4 [ 2987210 ] |
| Workflow | Original: JAC Bug Workflow v2 [ 2781291 ] | New: JAC Bug Workflow v3 [ 2894784 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JAC Bug Workflow [ 2736004 ] | New: JAC Bug Workflow v2 [ 2781291 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2391325 ] | New: JAC Bug Workflow [ 2736004 ] |
| Labels | Original: affects-cloud affects-server bugfix jira-integration loyalty macros-jira | New: affects-cloud affects-server jira-integration loyalty macros-jira |
| Labels | Original: affects-cloud affects-server bugfix jira-integration macros-jira | New: affects-cloud affects-server bugfix jira-integration loyalty macros-jira |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2271251 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2391325 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2221469 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2271251 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2165969 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2221469 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 1929957 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2165969 ] |