As per this stands resolved - does it work with Jira cloud ?

i need system fileds to be shown in wizard which I have made madatory while creating Issue using macro/Jira Issue

@Sumit Kumar, see the comments in this issue. This issue is about adding support for required fields of the specified types only. There are other field types which are not (yet) supported. For instance this issue tracks one of these cases: https://jira.atlassian.com/browse/CONF-32906
If your issue is with one of the mentioned field types in the description, then maybe get in touch with Atlassian support to check out whether it's a regression or some other problem.

I have Confluence 5.7.5 with Jira Macros 5.6.12. It is still not working for custom fields.

Are there any changes needed to be done to enable custom fields.

Thanks,
Sumit

I have installed the JIRA Macro v5.6.3 on a Confluence Standalone 5.4.
We are still asked to create the issue directly into JIRA whenever there is a FixVersions or a Text box field required upon creation.

I agree, a lot of people require this improvement to us.

select list could be a nice improvement.

what would be really excellent is the ability to convert tabular data into Jira tickets. It seems like this would be an extension of the Jira Issues Macro where the macro would create a table. Each row of the table would have a 'create issue' button. This might get around some of the challenges in this current ticket of customizing the form, because you could make the Macro user specify the columns in the table.

Iniitially, maybe only for text fields until you could sort out the validation.

It would be really awesome to have a staging area for issues/stories where you can edit and tune them prior to creation.

Hi Truong,
i did as you mentioned, but one question is still open:
What are "basic fields"? Is this non-custom fields? Is there any list (in the docu) available?

Thanks & regards,
Hans-Hermann

I have just updated title and description of this ticket to make clear. "all fields required" is huge and indefinite. So we would better separate each individual request for each other custom field type.
hhunfeld: Track your Track Clarity ID simple dropdown field (Select List (single choice)) in this ticket CONF-32906

Hi David – as a software developer myself, I do always chuckle when I hear the phrase "it can't be that hard." This is the classic complaint of software product customers – the things they want are easy, so why doesn't the software maker just put them in? I'm fully prepared to believe it can indeed be that hard – but the need still stands.