Create a Jira issue from Confluence with required fields

[Troy Johnson]

According to this article, I should be able to display required fields for a Jira issue in the Create Jira Issue dialog from within Confluence. I have read over the article, I've made sure that my field configurations are setup with the required field visible on the screens and Confluence appears to recognize that there is a required field because it presents me with the following message when I try to use the Create Jira Issue link :

Am I missing something or is the article wrong/outdated?

I'm currently using Jira Server 7.13 and Confluence Server 6.13. Any help/insight is appreciated. Thanks in advance!

[Deleted user]

Hi, did you find any solution?

[Troy Johnson]

@[deleted]

Unfortunately the answer is no. Still stuck in the same situation.

Troy

[Steven F Behnke]

What type of field is Customer?

[Troy Johnson]

The "Customer" field is a Select List (cascading). I am also seeing this behavior with other fields as well such as the Tempo Accounts Custom Field which is the one that immediately holding me up. I have not seen this ability work with any required custom field.

[Jan Dupont]

@Steven F Behnke Did you find a solution for this by any chance? We have the same problem with tempo custom fields (account in our case) and I would really like to have this ability via confluence.

[Troy Johnson]

@Jan Dupont I haven't been able to find a solution to this. Nothing from the community and nothing from Atlassian. Seems that it is a bug not acknowledged or this issue has gone under the radar.

[Jan Dupont]

@Troy Johnson I contacted Atlassian support and they referred me to this feature: https://jira.atlassian.com/browse/CONFCLOUD-31867 

Let's all vote and hopes it becomes a priority.

[Troy Johnson]

Thanks @Jan Dupont . I've added my vote and two cents to the thread.

[Steven F Behnke]

AFAIK they whitelist only some standard fields to render on the Confluence view, which is why non-whitelisted fields kick you back to Jira. Apparently neither cascading nor plugin fields are whitelisted.