Nic Brough -Adaptavist- Expert

What do you mean by "spool"? What would "spooling" look like for the end-user?

Codecov is not used as part of the products, but it is used to check coverage on some of their code bases. So, no, my understanding is that your data is not at risk of exposure, as it's a step away from where the security hole is. But Atlassian data about us might be. I think this is one that Atlassian should answer, as…

Encryption always imposes load on a process, so yes, it will be making everything slower. But not noticably, and the slight load it imposes would not make pages load any slower. If you could measure the extra time something takes, it would appear in the time between "user asks for page" and "server starts to give page to…

It's just confluence. Pronounced the same way you'd use the noun in a sentence that's not using it as a product name. "There's a good pub at the confluence of the Thames and Fleet" for example.

The log referral number is not an error message, it's just a marker to help find the relevant section log. This error can happen when you've got damaged data in the database (usually happens during an upgrade, but there are other ways to damage the data).…

The pricing pages work fine for me, what page were you looking at and what errors did you see?

Yes, as long as the parent issue is in the right status (i.e. not closed - it's nonsense to have a closed issue with open sub-tasks). If that is right, you can complete the sprint, and the open issue will move into the next sprint, as it needs more work (or its sub-tasks do)

Swimlanes are not displayed when they are empty. Your swimlane "label = CRMHC and issuetype = story" is empty because all the issues it would display are being displayed in swimlanes higher in the list. (Specifically, "issuetype = story") Cards can only appear once on a board to avoid confusion, and Jira executes the sort…

I do not understand what you are asking about here. >if the status of the source subtask exists in the target workflow, the step of defining the target status is skipped, whereas it is possible that it has to be changed. I cannot work out what you are talking about here, other than it's something about the relationship a…

Create page and edit page are the same permission, you can't grant them independently. If a person can edit pages in a space, they can also create them.

That means Jira can't connect to your database because the settings are incorrect - it looks like there is a database there, but the encrypted password is wrong in the settings file.

What do you mean by "with JQL query"? A post-function is an action that does something when a transition is executed. There are uses for JQL in post-functions (for example "find all the subtasks and update one of their fields"), but your question contains too little information about what you're trying to do to tell me if…

A sub-task is a part of its parent issue, not a separate issue. So if an issue "belongs" to a team, logically, any sub-tasks of it do as well, because they're a part of the issue. So you can't edit the team.

That could only happen if you've customised the code to make it detect where you're editing. You'll need to talk to your admins about removing that customisation.

To drop a status off a board, go to board config and then "columns", find the status and drag it over into the "unmapped" column. This only applies to company-managed (classic) projects though, for team-managed (next-gen) boards, you're not expected to have off-board status, so you can't do it (this hasn't changed)

Yes, the operations being mentioned there are technically separate and the code in Jira checks permissions for each separately, but there is some entwining. There was a time where you could do things to a Jira issue without actually being able to see it. Imagine that you grant me the permission to edit issues in a project,…

It's the line in the backlog that you can drag up and down over the issues ranked at the top of the backlog to define what is going into the sprint.

This is one that makes sense when you hear it, but I think is not in a very intuitive place and it's hard to find when you first need it! Go to Admin -> System -> Project Roles and check out each of the roles "manage default members"

Ok, that makes sense now, thank you. I'm not familiar with glidr, so I'd suggest you do what the last paragraph of the article suggests. I quote "Solve the product-engineering gap once and for all. Try GLIDR for free and if you’re a Jira user, install the integration and learn more from our Help Center.…

The link is wrong. Could you explain what your question is, instead of pointing to some other discussion that doesn't mention dual track?

This happens when you reconnect Confluence to an empty database, or damage/remove the config file the database connection is stored. Check that the file <confluence home>/confluence.cfg.xml contains the right connection settings for your Confluence database.

You can't change the level of an issue type. What you'll need to do is create a new issue type at the right level and then use "convert to issue" on every issue that needs to move up to a standard type. As they will no longer be sub-tasks, you won't have "child of" links any more, so you'll probably want to add an issue…

I suspect you are in the wrong place. Dual Track is not something I recognise as being an Atlassian thing. Could you explain more?

https://confluence.atlassian.com/confeval/development-tools-evaluator-resources/bitbucket/bitbucket-bitbucket-server-vs-bitbucket-data-center is probably the starting point for your reading.

You can't do this as described, the whole point of the column is that it groups together issues in the same status. You can do it though, but you'll need to have two separate status for testing, one in each of your separate columns.

Export/import is indeed the easiest and safest way to do it. But it only works for small and medium Atlassian systems - if you have a huge system, it may fail to export, and then you're into the nightmare of having to do it piecemeal or worse, by having to write SQL conversions of some sort.

Every change to an issue causes it to be re-indexed. There's also the option for a human to kick off project, background or locking index runs. This task specifically will not be scheduled, but it could be caused by any of the four actions above.

You need to escape the \ characters on windows machines, the OS is terrible at naming things properly.

Classic projects don't have group-by, they have swimlanes, but it is similar - a swimlane groups issues together based on something, and assignee, epic, story and project are hard-coded options. You also get "queries" though - you can build your own swimlanes with JQL and be very clever with it - I've seen boards that do…

This suggests you have a different field configuration for the sub-task issue type, and that it is using a plain text renderer for the description, rather than a rich one