Robert Wen_Cprime_ Community Champion

According to this support page (link here) you need to be the admin of the Bitbucket workspace.

@Arjun . You look like you're doing everything right, so I need to ask some specifics: What version of Jira are you running? What type of project is this? (Core, Software, Service Desk/Management?)

Found it. Missing a comma in the custom body data. Thanks for helping me out!

What are the last few lines of atlassian-jira.log? Maybe it can provide a clue.

Yeah, somehow the validation is missing that objectID. Here's what I have for the URL: https://api.atlassian.com/jsm/insight/workspace/<workspaceID>/v1/object/{{AssetList.key}} Anyway, I'm off to debug using Postman. Any tips?

Is there anything in the directory @Nic Brough -Adaptavist- specified? (F:\Program Files\Atlassian\Application Data\logs)

It depends on the type of test. SAST (Static Analysis) scan the source code to find errors and security vulnerabilities. Dependency scans are done either before or after a build. They scan libraries to see if security vulnerabilities exist. Dynamic Scan (DAST) are run against a build on a test server. BDD tests are also…

In Jira Server, default issue types can be set. If you don't specify an issue type (like Minutes), it will set the issue type to the default. Are you setting issue type in your REST call? It is one of the fields that you can define.

Hello @Arjun . What's the default issue type that is set for your Jira project?

Hello @chandag ! Yes, you're getting the gist. Once a commit happens, unit testing should happen automatically. Other checks such as listing could occur at this stage. If the tests pass, the commit is allowed. You can also automate the merge of changes back to a higher-level branch (including master/main). More tests…

To integrate JFrog to your Bitbucket pipeline, you have to be in the YAML editor (I get there by selecting "Create first pipeline". On the right, I expand the section for Pipes. I then do a search for JFrog. This is what I came up with: Once you've added the pipe, you should be able to follow JFrog's instructions for the…

Hello @karandaid Take a look at the Upgrade Guide. It'll help you out as far as OS, database, and other things. https://confluence.atlassian.com/bitbucketserver/bitbucket-server-upgrade-guide-776640551.html

Here's what I see when I try to validate the command

I don't think I am. I'm following the following: https://confluence.atlassian.com/jirakb/update-insight-object-status-to-expired-using-automation-1072219008.html Where do I include that?

I'm almost there. The if condition passes, but I get a 401 error on the Send Web Request. I created the API token, appended my email to it and base64 encoded it and added it as the value for Authorization along with the word "Basic". Am I missing something?

@Pramodh M is correct. Bitbucket Cloud has deprecated using your account password for logging in via HTTPS. Here's the notice: https://bitbucket.org/blog/deprecating-atlassian-account-password-for-bitbucket-api-and-git-activity New users need to create an app password and use the app password for doing git operations. Here…

So all looks good? If so, I'm glad. For your next attempt, go through the Upgrade Guide and understand that some dependencies (like the database) may need to be upgraded first before upgrading Confluence. Good luck with your next upgrade!

Yes, it looks like there were some writes to the database during the upgrade process. Shut down Confluence. Restore the database with the backup from 2 days ago. Restart Confluence.

One more thing: Did you consult the Upgrade checklist to make sure all the dependencies are covered? https://confluence.atlassian.com/adminjiraserver/upgrade-checklist-966063320.html

Hello @Manfred Hueskes ! Welcome to the Atlassian Community! Do you have any output in logs? Check the following directories: F:\Program Files\Atlassian\Application Data\JIRA\log. Logs will be a file of the form "atlassian-jira.log" Catalina.out should be somewhere around here - F:\Program Files\Atlassian\Jira\logs

OK 1. Copy/verify that the contents of 2022_02_03-Confluence-7.2.0-back\Confluence are in C:\Program Files\Atlassian\Confluence - That is the root level of your install directory. 2. Copy/verify that the contents of 2022_02_03-Confluence-7.2.0-back\Confluence are in C:\Program Files\Atlassian\Application Data\Confluence…

So that looks like the heading for a Portal Group? You can make adjustments by navigating to Project Settings->Portal Settings on the sidebar and selecting Portal Groups on the page.

You're welcome! Glad I could help!

Have you looked at your Import configuration inside your Object Schema that uses the Discovery imports to see if the Object Type Mapping inside the Import Configurations has the software items you want listed? If not, you'll probably have to include them. If you don't have attributes defined in your Object types, you'll…

@Juan Ramirez : I need the following since I'm not the one in front of the computer: Screenshots of: The directory structure below C:\Program Files\Atlassian so I can verify - The install directory - the Confluence home directory What the services panel looks like. In the meantime, for when you try to do the upgrade again,…

I don't think the executable allows you to downgrade (puts the 7.2 install back). What I think you need to do is keep everything as it is and manually set up Confluence 7.2 as a service. Here's the documentation for doing…

Yeah, Jira's LTS is already at 8.20. Confluence 7.17 LTS? :-)

That's probably the Confluence home directory. The installer prompted you for a destination directory. Do you remember where that is? Maybe you should see if there's a Confluence directory in C:\Program Files\Atlassian. That's my bet where the install directory is.

1. Shut down Confluence 2. From your backup, replace the contents of a. install directory b. Confluence home directory 3. restore database (probably not needed) 4. start up Confluence

Well, SQL Server 2008 is not supported by 7.16. It accepts SQL Server 2016 (deprecated), 2017, and 2019.