Nic Brough -Adaptavist- Expert

The standard advice here has not changed really. For a plain Jira core installation, you can consider a "component" to be a "sub-project". The other thing to look at maybe categorising your projects, so that they're grouped together as "sub-projects" themselves. In fact, there isn't really any concept of a "sub-project" -…

Yes, no change.

Beginning of 2020. See https://confluence.atlassian.com/cloud/blog/2020/02/managing-trello-accounts-from-your-organization

That sounds like it should be done as your workflow, not separate issues.

It's not, it's a list of attachments only, with references back to the pages they are attached to.

It sounds like a bug, but I think there's something wrong somewhere else - A developer would have had to have specifically sat down and written code to make it behave like that, and I can't think that any developer would have. Bugs are usually there because something is wrong or has been missed, you'd actually have to…

JQL is not SQL and it does not need joins as it sees every issue as a blob of data, as though there were only one table. To get all the Epics and Service requests, you can use almost exactly what you've said - issuetype in (Epic, "Service Request") I'm not sure whether you mean you want the issues on the other end of a…

That's not a confluence url, it's a settings page in your browser. What happens when you go to the Confluence page you were trying to edit?

When I've seen this in the past, the log has told me what page they were attached to, but if you are not getting anything out, then you might have to do this by force. Read the whole attachments table in the database and check for the physical existence of every file it says is attached.

Ok, but that does not change the answer - you need to fix your network or email server.

Confluence doesn't have anything like "lock" functionality, so I'm rather stuck on understanding what you are seeing here. The closest I can think of is that there are restrictions you can add to a page, so if someone else has added a "only people/groups of X can edit the page (and you're not in that rule)", that would be…

You might be able to do it indirectly, but the short answer is "no". There's no way to tie a permission to a sprint. What you can do is tie the permission to log work to a status. With workflow properties, you can say "jira.permission.work.denied" on a status, so if your workflow matches the the way the sprint works, you…

The project "field" is not text, there's no string pattern matching in JQL for it. I think you'll have to explicitly name every project in the JQL.

Behaviours can't do this, the landing place post-creation is done in code. There is a simple way to do it though - turn the project into a non-servicedesk project. As you're not using the portal, turning it into a Sofware or Core project would mean people use the issue creation screen and then use the issue view as you…

You can not. The keyboard shortcuts are hard coded.

They should not have been reading the logs from the DB, for precisely this reason.

You can create an automation that will fill in the original estimate when an issue is created.

JQL doesn't support that function as yet, you will need an app to provide it.

Sprints do not belong to projects, they belong to the boards within which they are created. If you want to only see issues in sprints A1, A2 and A3, then you need to amend your query so that selects only those sprints, and ignores other sprints. So: project in( A,B,C) and sprint in(A1, A2, A3) ORDER BY RANK ASC

Possibly. Users are not counted by what space they have access to, the count is done by them having access to your Confluence system. Archiving a space has no effect on the users granted permissions to use the space.

Both. You will need to pay for the people who use the system.

I can't see what is unclear about the pricing. Your users are simply anyone you choose to have use the system.

There is no way to do this, there's nowhere to apply validators in the "assign to someone" process. Also, you should never be setting a sprint like that. The sprint is decided by the team who are going to be executing it at the beginning of it.

Take a look at the permission scheme for the project. That holds the rules on who can delete issues from the project.

See https://www.atlassian.com/software/access and https://www.atlassian.com/software/jira/service-management , they both have links to a pricing page for the products.

What do you mean by "browser issue permission"?

See https://confluence.atlassian.com/confeval/jira-service-management-evaluator-resources/jira-service-management-the-difference-between-jira-service-management-and-jira-software-core They all have APIs available at the same place, but because they do different things, they are different calls.

It will be free as long as you don't go over three agents.

You have not told us what you are stuck on, what you are reading to try to fix it or what the problem is. So we can't help you, we don't know what you're looking at, other than there's something wrong with indexing.

That's warnings from later on, when it's trying to shut down. You need to be reading the errors from where it's trying to start up.