Robert Wen_Cprime_ Community Champion

Have you thought about rebuilding the indexes? If you're sure that the upgrade didn't touch the data in the database (which I'm sure it didn't), this would be my next step. Instructions on this link: https://confluence.atlassian.com/confkb/how-to-rebuild-the-content-indexes-from-scratch-on-confluence-server-110035351.html

This can be done if you're the organization admin. You have to go in and cancel the subscriptions you don't need/want. Details are at this KB page: https://support.atlassian.com/subscriptions-and-billing/docs/cancel-your-site-subscription/

This could be related to permissions. For the project in question, do you have the Delete All Attachments or Delete Own Attachments permission?

If you're really concerned about licensed users, the easier way is to remove them from the group that defines product access. The standard group is "confluence-users". Deleting users presents its own set of challenges, especially if you want to retain history of who created a specific page.

There's a specific Windows installer package you have to download from Atlassian. I believe it uses the Windows Installation wizard. Detailed upgrade instructions are here: https://confluence.atlassian.com/doc/upgrading-confluence-4578.html

A couple of questions... 1. Did you set the INSTALLATION_DIRECTORY variable inside the script to the root directory where Confluence is installed? 2. Are you running the script as the owner of that directory?

I've spoken to my clients and the company I work for has continually spread the word.

Hello! We've been talking about this exploit here: https://community.atlassian.com/t5/Confluence-questions/No-access-to-Conlfuence-Webpage-100-CPU-usage-from-quot-dbused/qaq-p/1793393?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_answer&utm_content=topic There was also a security advisory last…

This sounds a lot like your Confluence server has a virus.

You should be a member of the "Jira-administrators" group to be a Jira admin. And yes, if you created the board and are owner of the underlying JQL filter, then yes, you should be the board admin.

This discussion has the snippet from documentation. You'll need to have the Jira admin or board admin do this for you. https://community.atlassian.com/t5/Jira-questions/How-to-change-a-board-administrator/qaq-p/96223

To "pile-on" to @John Funk 's point, if the project you're looking at is a team-managed project, you'd need to have an Administrator role for that project. It appears you don't, because you'd see a "More Options" [...] button at the top-right.

Can you tell me if this is a team-managed or a company-managed project?

I'd ask you to double-check the IP addresses you put on that Jira page. I see: a CIDR range of public IP addresses with roughly 65536 possible addresses b. single IP address c. CIDR range with 64 possible addresses (this is not on the same subnet as b)

Are you sure the IP addresses are correct for your Confluence server? Other possible reasons are in the following KB article: https://confluence.atlassian.com/confkb/unable-to-connect-to-jira-for-authentication-forbidden-403-728139630.html

Do you have the screenshot of the Jira page to set up the Confluence user and password (and IP)?

Done!

Maybe you should add an additional condition: and no parent ticket is linked to the task. An additional action would be to link the newly-created parent ticket to the task. That way, it stays to a 1:1 mapping (which is what I think you want).

There's a variety of ways to create a new issue based on some action. You could look at: 1. Automation that performs issue creation when the task is updated to meet your criteria. 2. Scripting (may require an app like Scriptrunner) to execute from a workflow post-function. Hope this helps.

I think the main problem is leadAccountId. I'm not using the correct format. I think I have to use dot notation to get at accountId inside the field.

I think I'm close. I looked at https://community.atlassian.com/t5/Jira-questions/ScriptRunner-Cloud-Getting-fields-for-issue-takes-too-long/qaq-p/1597099 and it showed me how to specify the fields I want using queryString. The static analyzer doesn't like the "value" in each statement for the fields. Anyone have any…

This is what I see when I configure the Object Schema: Is this because this is the Cloud version of Insight? Another variable could be that I'm currently using a trial license.

Could you elaborate? I'm not seeing this in Insight for Jira Cloud.

Thank you for the update!