Nic Brough -Adaptavist- Expert

Go to Admin -> Applications and look at the group(s) named as able to use Service Desk. Remove people from those groups and you'll see the agent count go down.

That's a portal that leads you to one of several systems - which one did you end up in?

The same. Your "new project" is not new by the time you get to configure it, you're changing an existing project. Same for older projects.

The alternatives to the app Christian has suggested are other SSO enabling apps you'll need to add. Frankly the one Christian mentions is right at the top of the list of ones I'd recommend to do this. The issue collectors are using a non-authenticated session to set some defaults and they're making very specific…

That's old code and won't work in later versions of Jira, they don't work the same way. What are you trying to achieve with this?

What is the source Confluence? Cloud, Server or DC? Same for target? And what are you exporting and importing - a full backup or spaces? I'm afraid I can't read Cyrillic languages, and I can't paste the text into a translator. Could you give us the plain text of the error or translate it for us?

You will be charged for the tier of users you have, but this is complicated by multiple applications. You have three things to count * Each service desk "agent" * Each Jira Core user * Each Software user You can see your current usage, and what group memberships are granting the usage by looking at Admin -> Manage…

Open the project configuration and go through each setting, selecting "use another scheme" for each area you want to change.

Where did you raise these issues?

You already have Jira Core. You can't use Jira Software without Core - Core is the platform Software runs on. You don't need to do anything at all. Even your licences cover it - a Jira Software licence includes access to Core.

You'll need to raise this with Atlassian over at https://support.atlassian.com/contact (they might start by asking you to try another browser, may be worth testing that and including the result in the initial call)

Have you tried any of https://marketplace.atlassian.com/search?query=netsuite ?

No. Status is not a simple field, it is a human-friendly display of where an issue is in the process (workflow) You are creating new issues with this macro, so they belong in the status you are using to show "this has been created but not looked at yet".

I'm sorry that your design team have moved to a weaker tool, it must be a right pain having a team that's not working properly with others.

Cosed issues should not be in a backlog - the backlog is for stuff that needs doing, not things that are finished with. As for other places you can't see them, they're probably selecting for stuff that needs doing as well.

When you translated your question into a query, you dropped all the grammar that enables it to be understood as you intended. Punctuation really is a lot more important than you think (my favourite example of why it matters - "Let's eat, Grandma" vs "Let's eat Grandma" - it really is important to get it right...) When…

It could be either - it depends on what and how you are testing your products.

That's about deactivating an entire site, not removing one component.

Confluence is a good place to write stuff, but here, you seem to have a process for managing publication, which is not so much Confluence's remit. I think my answer is conditional on your process. Broadly, there's two approaches The light approach is a process where you just educate people that "it's not approved until the…

I think almost all of us look for a delete button. The remove method does make sense and it is horribly simple, but maybe a little too much - as it make me have to think!

Your assumption seems right - it's trying to connect to a Crowd that isn't there any more. I think you might need a local admin - you can get one by following https://confluence.atlassian.com/doc/restore-passwords-to-recover-admin-user-rights-158390.html

You will need to work your way through all the Jira code and the code for all the apps you are using to find out where this is used and change all of them to match your new scheme This will, of course, cause you massive problems on upgrade, ket alone the rest of the day-to-day problems. I would very strongly reccommend…

I am sorry, that was blunt and lacking explanation. You have told us that your xml contains "values that are encrypted". My response was based on the fact that there's no encryption in the workflows, so I do not recognise "some values are totally encrypted". If there are encrypted values going in to them, then that is…

Part of me wants to delete this answer as it is a really really bad thing to do. But it is an option if people need it. It's missing a lot of places though. Most places in Jira will still refer to "issue(s)"

No, Jira is handling the users, not the apps you add.

@Mohamed Benziane - I hope you don't mind my edit to your answer here. I wanted to emphasise that you had used the exact words that need to be looked for. I thought the bold might help do that.

I can't see a way to do that on Cloud. You may have to do some data analysis with the aim of reducing lists to the minimal useful reporting values.

I don't think it's possible with additional apps. A blunt way to look at active usage of the system is to look at the list of users by "last login time" in the admin -> users pages. Primitive, but a start. Usage of apps is a lot harder. You can, in later versions of Confluence, do the obvious check - look at the macros…

Jira Software does not look at Resolution like Jira (core) does. It looks at its "definition of done", which it sees as "the last column on the board". Have a look at the board's column mapping. For what you have said here, you need the status "Discard" and "Done" in the last column.

Both of those documents have worked fine for me, many times, whatever the certificate source. (There were some additional pain points caused by MS ignoring standards as per tradition, but they seem to have stopped that early last year) I think you need to give us more detail on where they are going wrong, and what you are…