Feature Query - IFTTT - Create Issue - Check User Account Feature (DC)

[Matthew Martin]

Hey Alex,

I've been encountering a lot of issues lately related to active accounts as we tighten up our license removal functionality.

We independently remove the Confluence/Jira licensing group from user accounts based on inactivity separately from marking an account inactive so we get true usage numbers for our tools. However, this causes issues relating to forms that use the "Create Jira Issue" function. If a user doesn't have an active account or the license group in Jira, Jira will send a 502 back to Confluence and fail to create. Not only is this frustrating for the user, but the error doesn't indicate the problem or how to resolve it.

I wanted to ask if you have a neat idea for validating that a user can create the ticket in Jira on submission (be that permission or account state) and return a helpful message to the user in Confluence if this validation fails?

[Alex Medved _ConfiForms_]

May be you can set up a rule to lookup some issue or service in Jira when the form is loaded and set the response back. And in case it is not the one you expect you can show the warning field (and optionally can also add a validation rule checking the response once again)

This way you can make form submissions more predictable.

Alternatively, if you can have a security group that holds all users who have access to Jira then you can easily check if current user belongs to that group and act accordingly

Alex