Victor Tashkov Atlassian Partner

Disclosure first: I'm the developer of Estimation Poker for Jira. Adding to Alex's point, since where the agreed number ends up decides how much re-typing is left. Everyone votes hidden, on the work item or in a session over a sprint, the votes are revealed together, and the agreed value is saved to a number field as the…

Hi @Rasmus Ersmarker , Disclosure first: I'm the developer of Estimation Poker for Jira, which I mention at the end. Jira itself still has no voting on estimates, so it comes down to an app or an outside tool. One more thing worth putting in that side-by-side comparison, because the badge doesn't cover it: where the votes…

Disclosure: I'm the developer of Sign for Jira, a different kind of app, so just one note on the approval step. Locking the worklogs together with their billable state at approval is a good choice; it is what makes the approved figure hold. Natively, Jira has no timesheet approval at all, so that is a real gap you fill.…

Disclosure: I'm the developer of Sign for Jira, a different kind of app, so this is one angle from regulated teams. Natively, the usual workarounds are the ones you list: swapping the approver in Assets, a group or an Automation rule, and remembering to change it back. The record of who stood in for whom is the part…

Disclosure: I'm the developer of Sign for Jira, a different kind of app. A question for the Q&A: how do you handle the QA sign-off when it has to be evidence, not only a ticked box? Natively, Jira records who moved the work item to Done and when, and a checklist shows the steps were checked. In regulated teams (medical…

Disclosure: I'm the developer of Sign for Jira, a different kind of app, so this is only one angle on Day 4. Natively, the Day 4 review can live in Jira as a work item for the period: a transition to Closed that only the finance role can make records who moved it and when, and keeps the evidence out of email. Where a team…

Disclosure: I'm the developer of Sign for Jira, a different kind of app, so read this as one angle. Reminders are the right fix for the approver who forgot. Natively, a scheduled Jira Automation rule with a JQL condition can send a reminder on work items that have waited longer than a week; the per-approver summary and the…

Disclosure: I'm the developer of Sign for Jira, so I look at this from the signature side. Agreed on hashing content rather than files. Natively, Jira's work item history shows who changed which field and when, but nothing ties an approval to the exact values that were approved. That is the choice we made for signatures on…

Thanks @Zuzanna , that's a useful split. The baseline answers which version of the requirements was approved; the signature answers who signed, with what meaning, and whether the record is still the one they signed. The two fit together. In Sign for Jira the space admin chooses which fields of the work item a signature…

Thanks for the write-up, @Marion Lepmets _SoftComply_. Disclosure: I'm the developer of Sign for Jira, one of the apps in this space. The medical device example matches what we hear most often: after a cloud change, can you still show that the approval workflow did what it was meant to do? Natively, Jira covers a good part…

Disclosure: I'm the developer of Sign for Jira. To your question about a hard block: natively, the validator on the transition into Done is the only thing that says no, as you describe, and it checks fields rather than whether anyone stood behind the checklist. Where a team needs a named person to confirm the Definition of…

Disclosure: I'm the developer of Sign for Jira, a different kind of app, so take this as one angle. Congratulations on the launch. On requirement sign-offs in medical devices, the question we hear most is not only who approved what, but whether the approval counts as an electronic signature in the 21 CFR Part 11 sense: a…

Disclosure: I'm the developer of Sign for Jira. To your closing question: natively, your status-per-approver pattern with the transition limited to a person or group gets the who and the when into the work item history, and for one approver that is a fair answer. In regulated teams an auditor usually wants more: what the…

Disclosure: I'm the developer of Sign for Jira, so weigh this accordingly. To your closing question, how a regulated team proves who approved version N: @Jim M _Cahaba Forge_ covered the native side. A release created with "Require approvals before moving to Released" checked won't move to Released until its approvers have…

Hi @Maria Reisinger _MetaFrazo_ , Disclosure first: I'm the developer of Estimation Poker for Jira, which I mention at the end as one option. On the units question: the sum breaks first where teams keep their scale in different kinds of fields. Story points sit in a number field, hours in time tracking, and T-shirt sizes…

Disclosure first: I'm the developer of Sign for Jira, an app for the gap described below. Agreed that every change matters. There is one thing medtech and pharma auditors usually ask for on top of change history: proof that a specific person approved a specific version of the record. Under 21 CFR Part 11 that means an…

@Ulrich Kuhnhardt your question from last year never got an answer, so: yes, with an app it can. Disclosure: I'm the developer of Sign for Jira. It adds two workflow validators. One blocks a transition until the work item has at least one signature; the other blocks it until the person moving the work item has signed it.…

Agreed, "often both, one after the other" is how it usually works in practice. The approval step decides that the record can move on. A validator on the next transition (for example to Released) then makes sure it can't get there until the responsible people have signed it with their meaning. Thanks for the article, Ciro.

Thanks, Ciro. This is the map I'd have wanted too. One case it doesn't cover, for anyone in pharma, biotech or medtech: under FDA 21 CFR Part 11 or EU GMP Annex 11, an approval often has to be an electronic signature, not only a click on Approve. That means confirming your identity again when you sign, recording what the…

Hi @Joanna Ignatowicz , Adding one option for the part of your question about seeing updates while you're working in Jira, with a disclosure up front: I'm the developer of this app. Trudy's checklist covers why the emails and the bell may not arrive. Separately from those, Jira doesn't tell you on the page itself when…

Hi Dan, Adding one more option to Martin's and Aron's answers, with a disclosure up front: I'm the developer of this app. You mentioned that some tickets need discussion before anyone takes them, so "assign first" doesn't always help. That's the case I built Live Change Alerts for Jira for:…

For the electronic signature piece of your CAPA workflow — Sign for Jira can handle signed approvals at each stage. It includes workflow validators to enforce signatures before status transitions (e.g., ensuring root cause analysis is signed off before moving to implementation). Each signature uses a personal Signing PIN…

Great overview of what it takes to make Jira compliance-ready. The point about integrating audit trails directly into Jira rather than relying on external platforms really resonates — the fewer systems you need to keep in sync, the less compliance risk you carry. On the digital signature side: if teams need Part 11…