Nic Brough -Adaptavist- Expert

Ok that's definitely there in all the Jira systems I've got admin access on. I think the only way to get rid of it is to disable the module that provides announcements (not even sure that's possible from the UI), use an app to suppress it, or have some bug. I'd want to check the log for any related errors (I'd start with a…

I talked in generalisations before because there's not quite enough detail in your question to be exactly sure what you are seeing and what exactly you mean by "access". This may be easier with a worked example. * Imagine we have Alice, Bill, Charlie and Dave as people who might have access to things. They all have a…

You have said that you are using Jira Cloud, but you are reading a document that is about Jira Server and Data Center (8.19+). Could you confirm whether you are on Cloud or Server/DC (and the version if server/dc)?

There is no problem where it is. Boards do not contain issues, they are a view of a selection of issues. At the moment, your boards probably have the same selection, so they are showing you the same issues. If you then change one of these issues so that it is no longer selected by a board, then, of course, any board using…

This is a copy of another question, with a spam url added to it. Sneaky

Welcome to the Community. This would suggest that each account has been set up to be an "owner" (technical or billing) and/or the site admin on both products. There's nothing to "split" in this case, the accounts are separate and if you want to remove them from contacts, that's fine (but a site admin can't be partially…

That looks odd to me, I don't think it's been removed from 8.13. Have you tried the administration search? Box towards the top right of the page when you are in admin areas (not the quick search for issues, that's above it)

I think there might be a bit of a misunderstanding on how Resolution works here. A resolved issue is any issue with a resolved value set on it. An unresolved issue actually has null in the database, and displays as unresolved. Your query for "resolution was in (unresolved, empty)" may well be looking for resolved issues,…

Ah, I didn't mention this, but: The "field trash" thing only applies in team-managed projects. The field in the screenshot is a global field, for use in company-managed projects. These do not have a bin, and if deleted, really are gone.

We can't help you when you've not given us any information. Is Jira running? What do the logs say is happening? What are the symptoms of "unable to access site"? What else are you looking at to try to find out what is wrong?

You'll need to explain what these accounts are and what you want from a "linked account"

There is no "Jira Account" to cancel. You have an Atlassian account that you have told Jira can use it If you are a site admin, then you can remove that account from Jira access.

Edit the workflow, and find the arrow that represents the transition. Click on it, and you'll get the config box where you can amend screens, post-functions, validators etc. Yes, you can make global transitions (you'll see those as a black starting status of "All") or have shared ones (where a couple of status can move to…

Not quite. Your Atlassian account is a thing to identify yourself to a system, it's not the actual account in that system. You do not need to dump the Atlassian account if you want rid of one of the things it lets you into. All you need to do is get an admin (Jira or Site) to tell your Jira that you should not be able to…

You'll need to explain where you are stuck. We (probably shouldn't) and can't do your homework for you.

Ok, we'll need to explain the basics. Confluence is an Atlassian product, it is a wiki, often used for documentation, but easily used for anything where you need to write stuff. autoprint.atlassian.net is a Cloud service that includes a Confluence installation (the /wiki gives away that we're looking at the Confluence…

This sounds like it was a "transition screen" - you set these up in the workflow, it's a simple "what screen (list of fields) to display while someone is moving an issue from one status to another"

No, I have less access to it than you do. This Community is a place for people to talk about Atlassian stuff, most of us are users of one or more products, there's a smattering of Atlassians, but we are not support and don't have access to other people's stuff. We can try to help, but that does mean needing clarity on what…

So not "locked", but you've used the wrong status in some of your workflows. So, you want to change the name of a status to another status, but you cannot edit because you've used the one you want to change in other workflows. Edit the workflows that have the unwanted status in them, and change the steps with the unwanted…

What is stopping you from deleting it? Why do you think you need Atlassian to do it, if you're an admin?

It is permission based, so it might be down to a role. Check what the permission scheme for the project says about who has the permission to "move" and "edit" issues. You can perform a simple edit on the issue type IF the source and target issue types are configured identically. If they are not, then you have to use the…

There is no "admin maintenance mode" in Confluence, so I do not think you are looking at a Confluence install. Could you check and explain more?

Welcome to the Community! I would guess that the message is accurate. I think your search is missing the three sub-tasks because it says "project = xyz", but if you take a look at the line under "Modify issue type scheme", you'll see it says "shared by 2 projects". (I know, there's a lot on screen here, and it doesn't jump…

You'll need to explain "locked", as that's not something Jira does with status. To "revert", all you need to do is work out what the old name was, and go to Admin -> Issues -> Status and edit the newly named one.

When it is ready. Atlassian do not give us fixed dates for new releases, only a very very broad window. They don't want to release software that isn't ready, like most organisations do because they've committed to a date they can't guarantee. As the time approaches, you'll find the window narrows a bit, maybe going from…

Are all the issues (and their sub-tasks, if any) in the last (rightmost) column in the board when you close the current sprint?

Is your "done" column the very last (rightmost) column on the board?

OK, there's two things that could cause that. First, your local network settings are blocking access. You'll need to take a look at firewalls and security software (it may be that you've got something that does not recognise the new install as valid to run where the old one was) Second, the service is not accepting calls.…

You just need to change the connection settings (and you may not have to even do that depending on your network). There's a file in <confluence home> called something like confluence.cfg.xml - this holds (amongst other things) the database settings, which will include the host address which might be an ip address or a host…

I would look to https://confluence.atlassian.com/enterprise/long-term-support-releases-948227420.html for the next long term support releases. There is no "migration" needed for those though, it is still an "upgrade" 6.13.23 is the latest (and last) release for 6.13. It won't be supported from the day after tomorrow…