Ballon Apps Atlassian Partner

Hi Chandra, thanks for confirming. That rules out the bookmark, so it looks like the app page itself is failing to load, and only the vendor can see why on their side. Gebsun has its own support portal for Team Worklog Reports: https://gebsun.atlassian.net/servicedesk/customer/portal/1 If you raise a ticket there, include…

Adding to Matthew's answer: one thing worth checking is the approver's email visibility. If it's set to "Only you and admins" (Atlassian account > Profile and visibility), the emailAddress smart value comes back empty, so the rule has no address to send to. Easy to test: add a Log action before Send email with…

Hi @chandra mohan dasti , That looks like an old bookmark to a report from the Team Worklog Reports app (by Gebsun), judging by the dates in the link. Bookmarks like that often stop working after Jira or the app has changed, even when the report itself is still there. A few things to check: Is the app still installed? A…

Hi @w74230 , Adding to Arek's question, because the answer points to one of two different causes, based on Atlassian's docs: If admins also get the "Smart button has been removed" message when they click the button on the published page, the flow behind it has most likely been turned off, deleted or changed. Changing or…

Good thread, and Tobijas covered the process side well. The part that usually trips people up is knowing who actually had access on a given day. Role membership alone isn't enough: Browse Projects can also be granted to groups, single users, everyone with a licence or even anonymous users, so it's worth reading the…

Having a status called Done doesn't mean the workflow enforces howyou get there — by default, Jira lets users transition freely unlessyou add a validator. Standard workflow conditions can hidetransitions, but a determined user with edit rights can still oftenbypass them via bulk edit or API unless you use a proper…

That pattern shows up mainly with larger service teams where access is organized around a team or function rather than around individuals — an IT support group, a security team, a department running rotating shifts. As soon as someone moves teams, the original Request Participants list drifts from reality: nobody notices…

Disclosure up front: I work on User Access Review for Jira (Permissions & Audit) at Ballon Apps, an Atlassian Marketplace partner — so weigh the app mention at the end accordingly. On the sync question itself: I don't think a native way to keep Request Participants continuously in step with a group exists today, and two…

The part that will save you the most time isn't the approval, it's the lookup. Automation has no native SharePoint connector, so unless you're willing to build and maintain a Graph API call in a web request action, the source of truth living there means you keep doing this by hand. Two routes, in order of effort: 1. Get…

Late addition to a thread that's already been well covered by Marc and Gabriela on the percentage-property route. One alternative worth having on record: if you'd rather not hand-edit workflow properties (fair, given Atlassian's own warning), a fixed quorum can also live outside the workflow entirely — set per work item,…

Thanks for coming back on it — good to have that confirmed. Permission-scheme-level drilling is the part that's easy to underestimate. A review built on project-role membership alone produces a tidy list that quietly leaves out everyone who reaches the project through a scheme grant, and you tend to find that out only when…

This is a common pain point, and the native options you listed (Log in as user, REST API scripting) are the right starting point for smaller instances. Disclosure up front: I build Jira apps too, including one in this space, so take the below as one vendor's scar tissue rather than a neutral review. The thing that cost me…

Short answer: at the approval moment itself, this isn't possible natively — and it's worth knowing why before you build around it. Approval steps bypass workflow transitions. That's documented expected behaviour, not a bug: a validator or condition on the approval transition is not evaluated, so the approver can hit…

To be precise about where that feature lives: in Jira Service Management approvals are available on all plans, and approvers don't even need a JSM licence. In Jira Software and Jira Work Management they're Premium and Enterprise only, and only in company-managed projects — team-managed projects don't have them on any…

Hi Des, As far as I know, that "We support markdown! Try **bold**, `inline code`, or ``` for code blocks" text is a fixed placeholder from the underlying Atlassian rich-text editor itself, not a field-level default value you're setting — so it can't be edited or removed through the paragraph field's configuration. I…

I work at Ballon Apps. Adding to Dexter's answer with the concrete steps. 1. Find the stuck tickets. Jira Cloud searches by accountId, not by name or email; you can get the accountId from the user's profile URL (Atlassian has a KB for this: How to get the accountId for Customer Accounts in JSM). Two queries, worth running…

You can keep the multi-user picker. The restriction is now available at field level, which is a better fit than automation because it stops the wrong person from being selected at all, instead of catching it afterwards. 1. User filtering on the User Picker (multiple users) field For a long time user filtering only existed…