Raul Pelaez _QUABU SOLUTIONS_ Community Champion

Yesterday (afternoon) I tried too and all ok! Probably something has been changed in Atlassian or Cursor thanks to this question! well done Sam!!

I see some documentation of Cursor domain here https://support.atlassian.com/security-and-access-policies/docs/available-atlassian-rovo-mcp-server-domains/

Select Apps > AI settings > Rovo MCP server. Select Add domain and add the domain cursor://cursor.mcp/** ( from this documentation: https://support.atlassian.com/security-and-access-policies/docs/control-atlassian-rovo-mcp-server-settings/ ) More…

Exactly Florian, Select Apps > AI settings > Rovo MCP server. Select Add domain and add the domain https://example.com/** The thing is (I think) Cursor does not expose a public MCP endpoint like Lovable...

I vote Appwide Booking kings!!

Here an example of Jira JQL function HasInactiveAssignee compatible with Jira 8, the function is in the comments of the post https://mraddon.blog/2015/08/31/new-jql-function-custom-to-retrive-issues-with-inactive-user-in-assignee-hasinactiveassignee/

New source code for Jira 8 Syntax example: issuefunction in UserInRole("project = JIRA",assignee,Administrators) Here the code: package com.onresolve.jira.groovy.jql import com.atlassian.jira.issue.Issue import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.Issue import…

Ok Dmitry I will try!

Finally if you install the services without using the Google Cloud load balancer the process works fine. I have tried with Jira 8.2 and Confluence 6.15 and now is ok! That's the trick!

I have the same problem, but Jira is working well, but Confluence after configure the database (or configure the trial database) in the installation the system becomes broken in Google Cloud using the same instructions

The same big bug security issue is happening in Jira Server 7.13. The trace of the change of user Management sometimes is done by "JIRA" user.

The bug still in Jira 7.13.1 we have some users in the audit log inactivated using the user "JIRA" .... super big bug security issue

Try this example: https://mraddon.blog/2018/02/04/jira-groovy-postfunction-example-to-set-tempo-team-and-tempo-account-fields/

Try this: https://mraddon.blog/2018/02/04/jira-groovy-postfunction-example-to-set-tempo-team-and-tempo-account-fields/

WOW Amazing!!! Good job I will take a try

You can use this script https://mraddon.blog/2017/12/01/how-to-archive-the-old-releases-in-jira-of-all-projects-at-same-time/

You can use this! https://mraddon.blog/2017/12/01/how-to-archive-the-old-releases-in-jira-of-all-projects-at-same-time/

I have the same problem today. After update one script field, all the script fields are empty of code at this moment. Please help!!!

Cool!!

Really great add-ons!!

Tricks to block this URL from Jira: https://mraddon.blog/2017/09/30/two-tricks-to-improve-the-performance-and-security-of-your-jira-server-7-4/

Here some tricks to avoid this problem (and others) https://mraddon.blog/2017/09/30/two-tricks-to-improve-the-performance-and-security-of-your-jira-server-7-4/

The code for UserInRole JQL function: package com.onresolve.jira.groovy.jql import com.atlassian.jira.issue.Issue import com.atlassian.jira.ComponentManager import com.atlassian.jira.ComponentManager import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.Issue import…

Your Jira admin can create a Groovy Script field and show the report or assignee email in the tickets. This field can be shown after this in the filter results gadgets or in the Issue search screen. You can use ScriptRunner plugin in Jira Server or SIL Customfields.…

Hi! Use "New Status Colors" and "Kanban Combined WIP" to identify better the cards/tickets in dashboards, Agile boards, etc. https://marketplace.atlassian.com/apps/1214981/new-status-colors-for-jira?hosting=server&tab=overview…

package com.onresolve.jira.groovy.jql import com.atlassian.jira.issue.Issue import com.atlassian.jira.ComponentManager import com.atlassian.jira.ComponentManager import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.Issue import com.atlassian.jira.issue.search.SearchProvider import…

Hi Matias, the problem was solved with the upgrade. Thanks for the bug report

I need the same...

It don't works in JIRA 6.3.15....