nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Electronic signature on transitions in jira cloud

Dora Lukin

Hi, all,

does anyone know of a solution that could allow us to have electronic signatures applied during a transition?

There are plugins that do this in Server, but I have not found one for Cloud.

I am hoping I am missing something, because it seems a lot less practical to apply a signature on a state, than on a transition, so I'm not sure why this would not be an option in any of the plugins.

We are currently using the Digital rose plugin, but the process of applying the signature on a state, and only then executing the transition is so unintuitive.

I'm reaching, but perhaps someone found a good solution for this?

thank you

Dora

Accepted answers

marc -Collabello--Phase Locked-

Hi @Dora Lukin ,

Can you explain in more detail what you mean by a transition?

Chris Cairns - Digital Rose

Hi Dora,

@marc -Collabello--Phase Locked- is correct. The Jira Cloud environment and API's are more restrictive than Jira Server in what parts of the Jira workflow apps can hook into.

For our eSign app that means we can not interact directly with the transition views within Jira cloud. Instead users have to execute 1 or more signatures pre-transition, and then make the transition. Many of our customers require multiple people to approve so an in-transition option would likely not be feasible for them. eSign does offer a validator that you can add to the Jira workflow to ensure signatures are captured before the transition. (ie. Basically it is a rule that blocks the transition and warns the user if there are still outstanding signatures)

If and when Atlassian expands the Cloud API to allow Apps to work within transitions, we are prepared to add this to eSign.

Let us know if you have any questions

Regards,

Chris

Chris @ Digital Rose
eSign for Jira, eSign for Confluence

PS. It may not directly help your use case, but we have just released Bulk Invite support for eSign and have Bulk Execute in development. This is a way to improve user efficiency by inviting/signing many Jira issues at once. See eSign Recent Changes

All comments

marc -Collabello--Phase Locked-

Hi @Dora Lukin ,

Can you explain in more detail what you mean by a transition?

Dora Lukin

hi, yes, I mean, I would love to execute the signature (insert credentials) on the transition screen

marc -Collabello--Phase Locked-

Ok. If I understand this correctly, this is not supported in Jira. I believe apps can not directly hook into this screen.

Dora Lukin

Is this inability somehow related to Cloud specifics?

On server there is this option (I guess it's a custom field that is added to the transition screen)

Es on serveer.PNG

Chris Cairns - Digital Rose

Hi Dora,

If and when Atlassian expands the Cloud API to allow Apps to work within transitions, we are prepared to add this to eSign.

Let us know if you have any questions

Regards,

Chris

Chris @ Digital Rose
eSign for Jira, eSign for Confluence

Dora Lukin

Thank you for the explanation, Chris.

I do understand the advantages of signing on the state for multiple approvers.

In our case it's just a lot more practical to sign the issue on the transition screen, especially for issue types that have a lot of mandatory fields on the transition screen, so users will populate all of them only to then get the validator message, because they always forget on which states they need to sign.

I guess they will get used to it eventually, but I'm also hoping the functionality may in time be available on cloud

Dora

Anne Mari

@Chris Cairns - Digital Rose have there been any changes to this that would enable us to add eSign to transition screens? We have a workaround in place but it is not ideal - users misunderstand it all the time.

Chris Cairns - Digital Rose

Hi @Anne Mari Nedevska Today it is still not supported by the Atlassian Connect app framework to inject an app frame into the Jira transition popup.

The eSign signature validator has a few more options now but essentially still works the same way. Jira will call the validator when the user completes the transition popup dialog and (Jira) will block the transition and show the error message if the required signatures are not present.

One new capability is that eSign now supports post-Signature webhooks. Some customers are using those to automatically transition issues to the next status after signing (via a Jira automation rule). Users would still need to "Sign" inside the issue view, but the workflow could hide the transition link so the users could not press it out of order and get the error message of Signatures required from the validator.

For an example of using an eSign webhook to trigger a Jira automation, see: How To Integrate eSign for Jira with Slack

Chris
Digital Rose

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud