David Yu Expert

Important to note that Insight only seems to fetch the first 1,000 filters available to you. So your filter might not show up at all in the list, unless you rename with metacharacters in the front of the name so it gets sorted alphabetically first. Ex: !MyFilterList. PS: Even after renaming my filter, I get similar results…

If you have ScriptRunner, use the Script Fragment's "Hide system or plugin UI element." Under "Hide what," choose: com.riadalabs.jira.plugins.insight:rlabs_insight_topmenu You might also want to hide the assets icon on Kanban boards: com.riadalabs.jira.plugins.insight:rlabs-project-jira-section Then under condition, you…

Doesn't the SLA logic for startOfDay(8h) create problems later on? For example, on Day 1, it'll apply the rules perfectly fine. On the next day, startOfDay(8h) won't match the issues it matched yesterday.

In case this helps anyone else in the future, the user likely dismissed the timezone warning prompt in the past. Once dismissed, it'll never prompt again. https://jira.atlassian.com/browse/JSWSERVER-25504

So how exploitable is the SnakeYAML issues on a private instance? It's not like we're letting strangers parse/upload YAML.

For the longest time, we've been asking for authentication on all public endpoints if it's operating in private mode. https://jira.atlassian.com/browse/JRASERVER-65521 I guess it's a hard problem to solve; but it would have reduced the severity of a whole class of CVEs.

@Tim Eddelbüttel @James Ponting with CVE exploits now already published on github, maybe it's safe again to re-open the sources unless there's more internal code auditing happening on them.

I guess this explains why source code access was recently disabled.

You can trigger an Automation from a Transition by calling it through a Webhook post-function So trigger a classic "Jira Webhook" which then triggers an "Automation for Jira" rule that is listening on an incoming webhook, right? I thought about that a little, and it feels a little risky having anonymous webhook endpoints…

Looks like this still isn't available yet today. Seems like the least kludgy options are to either write a IssueProperty during the post-function, or like someone else suggested here, create a bunch of new Jira events, and fire those events.

Response from support: You are correct, as described in Licensing your Jira applications if you exceed the Jira Software user count, the users won't be able to create new issues. For Jira Service Management, the behavior is a little different, you won't be able to add any more users than the license count for JSM. You will…

I can't test it yet because we're currently still testing with the eval license which is unlimited agents. Not having an easy time pasting the script here so here's a link to the snippet.

My two favorites are editing the user's group in Confluence when you have hundreds of groups, and trying to add a new project to a customfield context when you have 300 projects to pick from in a tiny 5 line window select list. Check out scrollbar size to see how long each list is. 😂 There's a skill required here to ensure…

This seems like a bug. APIs shouldn't require websudo.

It's a good addition! But a few questions I had also raised to support: Why not use native emoji fonts on the user's system rather than images (similar to what we're seeing here). It would make copying and pasting a lot easier, and rendering probably slightly faster. Also, the emoji fonts would scale sizes when you use…

Been trying to do this myself and here's what I've learned so far. The soy files are compiled into js files so modifying jira-servicedesk-3.11.1-REL-0014.jar /soy/ won't help. servicedesk-frontend-plugin-x.xx.xx-REL-xxx.jar is what you're probably after...try modifying he contents of the js files instead, rezip the jar,…

Would love to upgrade but we're still waiting on fixes for comment ordering which broke in LTS 9.X (JRASERVER-74191, JRASERVER-74122)

I clicked through the survey and it seems to be trying to determine if we'd still pick Data Center over Cloud (or move to a different vendor) if they greatly increased the pricing of DC so that it exceeds Cloud. It's things like this that makes users continue to question Atlassian's commitment to DC, as opposed to a survey…

@Filip Sagen see these two issues: * https://jira.atlassian.com/browse/JRASERVER-74191 * https://jira.atlassian.com/browse/JRASERVER-74122 and also this previous post. Personally we are holding off upgrades until these issues are fixed.

How was the session for those of us in the US West Coast that couldn't attend? 

I patched Component Watchers. You can examine the commits to see the patches. Use/test at your own risk, no support given, yada yada yada. 🎅

Sami, not sure what the problem could be. I tested locally on new 8.22.6 install and it worked for me.

Sami, you are welcome to test my patched 2.8.5.2 version against 8.22.6 at your own risk.

@Sami Ahmed Shaik what version are you currently using?

Ahhh, Component Watchers. Maybe if time permits, I will also patch that.

Hi Deigo, I see what you mean, the configuration menu is erroring out with a 405 method not allowed error. After some research, this is due to changes in Jira 9, in particular Verification of Jira web action request methods I've added the necessary annotations to the WatcherFieldSettings.class and recompiled:…

You've got to manually download and upload the plugin.

I patched a copy (2.5.8.1) of the watchers plugin but it's use/test at your own risk.

To answer my own question, support has raised this issue: https://jira.atlassian.com/browse/JRASERVER-74466

No, unrelated. I'm asking about what Atlassian chooses to collapse. In Jira 8, it collapses my oldest comments. In Jira 9, it collapses my newest comments which serves no practical purpose I can think of.