Martin Runge Community Champion

Hi @focusdoit Welcome to the Atlassian community. The filter in File Status just switches which Git states are shown, and Clean means tracked files with no changes against the last commit, so there is nothing to stage or commit. They stay hidden by default because the default view only shows files you can act on. Cheers,…

@Trudy P Claspill just wanted to link your article. ;)

Great to see this land here! Reasoning tiers are already standard in most AI tools, so the mental model transfers straight over. What I was looking for here is the cost side, and the article does answer it: Think Deeper uses more credits, with a warning for high volume or automated agents. So the tier is not a token saver…

 What a lovely photo, Kristján, and happy belated 90th to your mom. Making it to her birthday with almost the whole family there sounds like a very good day. My memories are mostly her behind a camera, and afternoons in the garden with my grandparents. But two stand out, and they belong together. The first is learning to…

Hi @羽鳥彩子 Hi Hatori-san, This came from the Atlassian incident on 27 August, when Jira, JSM and Confluence were unreachable in some regions. It has been resolved since, so please try your site again. Details are at https://status.atlassian.com Nothing was wrong with your site or your account, so there is no action needed on…

Hi @Alex the CTO I saw your comments on the other questions in the forum. As you probably know: This was the Atlassian incident on 27 August, where Jira, JSM, and Confluence were unreachable in some regions. It has been resolved since, so your site should load again. The entry is…

Hi @Muhammad Riandy This was the Atlassian incident on 27 August, where Jira, JSM, and Confluence were unreachable in some regions. It has been resolved since, so your site should load again. The entry is at https://jira-software.status.atlassian.com/ The message is generic on purpose, so it also shows up when the platform…

Hi @Henry Nguyen This was the Atlassian incident on 27 August, where Jira, JSM, and Confluence were unreachable in some regions. It has been resolved since, so your site should load again. The entry is at https://jira-software.status.atlassian.com/ The message is generic on purpose, so it also shows up when the platform…

Hi @Reeja Joy This was the Atlassian incident on 27 August, where Jira, JSM, and Confluence were unreachable in some regions. It has been resolved since, so your site should load again. The entry is at https://jira-software.status.atlassian.com/ The message is generic on purpose, so it also shows up when the platform…

Hi @Manikanta S, This came from the Atlassian incident on 27 August, where Jira, JSM and Confluence were unreachable in some regions. It has been resolved since, so your board should load again. The entry is at https://jira-software.status.atlassian.com/ Nothing was wrong with your account, so there is no action needed on…

Hi @Sophie Lu This was the Atlassian incident on 27 August, during which Jira, JSM, and Confluence were unreachable in some regions. It has been resolved since, so your site should load again. The entry is at https://status.atlassian.com The message is generic on purpose, so it also shows up when the platform itself is…

Hi @Lee This was the Atlassian incident on 27 August, during which Jira, JSM, and Confluence were unreachable in some regions. It has been resolved since, so your site should load again. The entry is at https://status.atlassian.com The message is generic on purpose, so it also shows up when the platform itself is having…

Hi @Arale Li That page is unavailable screen came from the Atlassian incident on 27 August, when Jira, JSM, and Confluence were unreachable in some regions. It has been resolved in the meantime, so please try your site again. Details at https://status.atlassian.com Nothing was wrong with your site or your account, which is…

Hi @Agnes Caruso Welcome to the Atlassian community! Good news: this was almost certainly not your integration cleanup. Your post lines up exactly with the Atlassian incident on 27 August, where Jira, JSM, and Confluence were unreachable in some regions. That has since been resolved, and you can see it at…

If you are checking https://status.atlassian.com/ now, the incident has been resolved, and others have started reporting their sites as operational again.

Good to hear.

Hi @Shirley Jones I don't have issues myself, but I believe it has the same root cause as this major incident: https://jira-service-management.status.atlassian.com/, as Assets has historically sat inside JSM. Your System Health is showing green because it only lights up once Atlassian scopes an incident to your…

Hi @Dobrowolski Piotr Leider noch nicht. Live-Updates findest du unter https://status.atlassian.com/ Cheers, Martin

Hi @Mohammed Faizal _Contractor_ This looks like the open Atlassian incident rather than something on your side. Since 27 August, around 04:22 UTC, Atlassian has been investigating issues with accessing products in some regions, affecting Jira Cloud, Confluence, and Jira Service Management. Live updates are at…

Hi @als6934, is this still an issue for you? If yes, the fork bomb message means git.exe is calling itself in a loop, so I would treat it as a broken embedded Git. Close Sourcetree, delete C:\Users<you>\AppData\Local\Atlassian\SourceTree\git_local, and reopen so it downloads Git again. If that fails, install Git for…

Hi @MARIANO GONZALEZ That message usually means the site was deactivated or suspended, most often because a subscription lapsed, was canceled, or the site went inactive on a Free plan, not because of a technical fault on your side. If it was a Free site, this article by @Trudy P Claspill explains how the inactivity and…

Hi @Min Kyu Byun Since this thread is a while back, is it still an issue for you? If yes, I would open Repository > Repository Settings > Remotes > Edit and paste the full URL only into the URL/Path field, because the double scheme in <a href="https://http//192.168.0.24/" target="_blank" rel="nofollow noopener…

Hi @Thomas Jones Welcome to the Atlassian community. My take is that "Jira" has no plural, and the reason is baked into its origin. Jira is a shortened form of Gojira, the Japanese name for Godzilla, which the team used as a nickname for Bugzilla back in the day. Japanese does not mark plurals the way Italian or English…

Hi @Winsome Tang Welcome to the Atlassian community! I would not delete the whole C:\Users(USER)\AppData\Local\Atlassian folder, since that also wipes your repository list. Instead, I would back up bookmarks.xml (and opentabs.xml) from the SourceTree subfolder first, then delete only the remaining state files, and restore…

Hi @Amir Colnect Is this still relevant for you? I would read the "Permission denied (publickey)" as a sign that the host key update actually worked, since you got no host key warning; what remains is simply that your own SSH key is not being offered to Bitbucket. On Windows, Sourcetree also keeps its own host key cache…

Hi @MacDisein Welcome to the Atlassian community! To see which account belongs to which server i would open Tools > Options > Accounts (on macOS Sourcetree > Settings > Accounts), because that list shows the host URL for each account and lets you map which identical username belongs to which GitLab CE server. There is no…

Hi @Don Hames The core issue is that CQL indexes content, not containers, so a space has no "last activity" field to query, and an empty space has no content rows to match. I would skip CQL and use a Send web request in the flow against the v2 API: page through /wiki/api/v2/spaces?type=personal, then for each space hit…

Hi @chunkitt.hong The message means Sourcetree could not pull the Git package from Atlassian's download endpoint, so I would look at the connection and the target folder rather than at Git itself. I would try in this order: * Update Sourcetree itself under Tools > Options > Updates, since a newer app version ships a newer…

Hi @Yama Kamyar Welcome to the Atlassian community! I would look at the remote definition rather than the release. The double scheme in the link tells me the host root URL stored for that remote already contains https://, and Sourcetree prepends it again when it builds the browser link. Which OS are you on, Windows or…

Hi @Stephan Stroetz Welcome to the Atlassian community! Yes, you can reinstall safely. Sourcetree does not hold your commit history. That lives in the .git folder in each repo on disk and on the remote. Sourcetree only keeps bookmarks and settings. Before reinstalling, I would rename %LOCALAPPDATA%\Atlassian\SourceTree and…