David Yu Expert

We are also waiting for support for approvals on Page Edits for this to be useful.

I know marketplace vendors complain about customers not updating their apps. I think this friction of not knowing what's different probably is a contributing factor. If apps want to incentive updates, they should make it easier to discover what changed.

The lack of a method for easily renewing tokens is going to be a big pain for us. It's so clumsy clicking through tens of scopes, and having to start over if you miss one. And trusting users to remember to renew guarantees some service will break in the future.

For users that are planning a Cloud migration around the same time this feature rolls out (May/June), is there a way for us to pause this feature on our instance until our migration is completed? We don't want to end up in a situation where the 1st migration occurs before this rollout, and our 2nd migration occurs after.

The odd thing is Field Configurations were never a performance problem in Data Center. Maybe it only became an issue in Cloud when they released "Field Layouts" so teams could customize their View/Edits screens even further? But then they didn't include Layouts in JSM projects? I don't know how to make sense of some of…

Sure I can understand performance aspect of it. Though many of the checks could probably be short-circuited when testing the customfield context configurations but I can only guess what's really happening under the hood. It was nice not having to fiddle with Field Config settings, but it now seems unavoidable.

We're doing cloud migration tests at the moment, and I can see several of our standard field configs approaching 500 fields already. This is because the fields would add themselves automatically to all field configs back in data center. Of course no project would have at their disposal all 500 fields, this is limited by…

I do have Atlassian Guard, I'll have to investigate that more but I didn't recall seeing any app allowlist setting there. There is a pending feature request though to pre-approve apps: https://jira.atlassian.com/browse/CLOUD-11676

Thanks, I shall give that a try. For the reprovisioning part, I think the user won't get instant access, and may need to refresh the page since re-adding back to the group won't be instant. But I think that's the best that can be achieved here.

The old links to my patched watcher plugin has been wiped because BitBucket no longer offers Downloads for free accounts. I've just uploaded a copy to the source repo itself in case people are still seeking out a Jira 9 or 10 compatible version. Test and use at your own risk!

How about using Script Runner to fire an IssueUpdated event (with no email). This is one less extra step (don't need to do two actions add/remove a label). I've hardcoded a filter-id here but can easily change it to any JQL. import com.atlassian.jira.component.ComponentAccessor;import…

I'm repairing my test 10.3.4 instance right now because the JSW upgrade button moved me to 10.4.1, instead of 10.3.4. Just reviewed my logs to make sure I didn't hallucinate: **************** Jira starting... **************** 2025-03-07 13:29:00,098-0800 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] ___…

Look closely again. It's pushing out a 10.4.1 (the latest bleeding edge version) on a 9.12.X LTS Jira install. They are not supposed to be marked compatible.

Paul, I looked at your add-on but I don't think it does the same thing. Distilling it down, I would need a real field that contains watchers so it can be used in places such as Issue Security Schemes. And the ability to add watchers bypassing Jira's normal security checks that prevent you from adding watchers if that…

I have one in the Downloads area you can test out. Let us know if you encounter any problems. You should take this chance to plan a migration to something better supported; I don't know how long I can keep duct-taping this thing together. 

To add to this, here's a failure mode to consider. Your are at your JSM agent limit. You reactivate a user that previously has the JSM agent group assigned. Whoops, now you're over the limit, and none of the JSM features work anymore. :-/

Would be great to see a roadmap for Proforma. Since the acquisition by Atlassian, it seems like features have stopped shipping. We could really use some API methods to update Proforma forms. The mixing of JSM Native fields + Forms is still sometimes awkward (try integrating attachments with forms for example).

Is a comprehensive performance test report available for version 10 yet?

Seems like a good start of the Anarchists Cookbook for Jira. I don't think I have anything too controversial to list, mainly use the DB for read-only maintenance tasks such as: * Deactivating inactive accounts * Find users without avatar pictures and syncing them from Slack * Automatically archive projects if they have the…

@Ella Hilton is this policy change for Cloud or Data Center?

It's easier now with scriptrunner HAPI: issue.set { setLabels { add('test') } }

With the addition of adding watchers during creation, I hope you can also implement watchers in issue security levels to complete the circle. It's simply clunky creating a multi-user picker field as a workaround when watchers works so seamlessly, and there's still quite a lot of community interest using a deprecated add-on…

Ram, ScriptRunner does a type check it seems and refuses to let you return a LocalDate object. Anyway, I think this is related to the Searcher ScriptRunner uses. If ScriptRunner supported *Date Range Searcher* in addition to *Date Time Range Searcher*, these problems would go away.

Here's a User Macro you can use to make a Banner Header for Confluence Data Center/Server: In addition, it supports text inside the banner image itself as an overlay. ## Macro title: Banner Image ## Macro has a body: Y or N ## Body processing: Selected body processing option ## Output: Selected output option ## ## This is…

Out of curiosity, what benefits have teams noticed since switching to OpenSearch?

Are you perhaps hitting this bug? https://jira.atlassian.com/browse/JSDSERVER-15024

If you have access logging enabled, then they would be located in your HOME directory's log folder. In addition, if you use a proxy like apache/nginx, there would be logs there as well. Hopefully they are not rotated out. If they are, then you are out of luck unless you are making backup snapshots.

I looked through the scriptrunner job example and it seemed a bit daunting. Anyway, I think this also works with just scheduling it as a cron + curl job? EFFECTORS='{"effectorId":[25,26],"structureId":2788}' RESULT_CODE=`curl -o /dev/null -w '%{http_code}' -u "$USERNAME:$PASSWORD"…

https://jira.getxray.app/browse/XRAY-9729 Was due to X-Ray add-on. Update: X-Ray believes it's something Atlassian introduced that's causing an interaction with plugin vendors, not just X-ray.

Getting an app approved for data center these days may be a bit too onerous for a hobbyist app developer. Might be the reason why Quick Sub-Tasks it's no longer listed for download (but an archive is still available here). We're still using it today on Data Center. If you attempt to run this in JDK 17+, you may get this…