Nic Brough -Adaptavist- Expert

As an issue tracker, Jira is designed not to lose information, such as the issues you are trying to track. Deleting issues is actually something that should be removed from Jira, it's a function that defeats the purpose of having an issue tracker in the first place. (Individual issue deletes, not "delete because the…

I would want to check that the account is still working first. Ideally, get them to log into it at https://id.atlassian.com and check everything is looking ok. Then I would want to check how your Trello is configured to let people into it - it sounds like you have got it set up to only allow people with accounts on certain…

On Cloud systems, you have the Admin -> Backup option that enables you to grab a file from the system that can be used to recreate your whole Cloud site, or migrate it to server.

JQL looks at multi-select fields as though they are a list of options (which they are). If you have an issue with Monday, Wednesday and Friday in the "day" field, then JQL will look at all three when you ask it "show me issues where 'day' = Wednesday", and hence it will return that issue.

Welcome to the Atlassian Community! This is what it says it is - you have an old user account that is no longer valid for your system. You cant re-enable an account that can't be used on your system.

Just to be clear, all released versions are "stable". Atlassian only releases "unstable" versions in their "early access" programme. "Stable" doesn't really have any meaning when talking about Atlassian software, or in fact, almost all software nowadays, it's a meaningless concept.

Map that deleted status into the last column on the board too, this will mean your sprint sees the issue as "done", so its parent can be marked done too, then you can close the sprint.

Thank you for clarifying that, but you have lead me to needing another one. Are you asking about how you might use Scriptrunner to create sub-tasks (with the same summary), or how to use JQL to find them? If it's a scripted create, I base all of mine on the script…

Are you trying to rank the sub-tasks outside the issue of which they are a part?

No, it means that team-managed projects do not use workflows via schemes. TMPs can have different workflows for each issue type in them - go into the issue types, edit one of them and use the "edit workflow" button at the top right. When you commit changes to a workflow, Jira will ask you which issue types to make the…

You need to talk to your admins about why they are disabling it.

Welcome to the Atlassian Community! Yes, cloning does what the name suggests - makes a copy of the current issue. There's no way to change what it does because it wouldn't be a clone if you changed fields. If you think you want to change fields during a clone, then you're actually looking in the wrong place - you should be…

/could you show us how you have configured this? It sounds like you have set it up to trigger on any change, not just transition.

The solution is to ignore whatever is telling you this. The service needs to be able to process methods other than POST for it to be able to do its job. 

Whatever you have that is telling you that no rate limiting is a vulnerability or that your confluence is doing it is wrong. 

Stop using the methods that are "dangerous". This doesn't have anything to do with Confluence, other than it being a web service you are running somewhere. It can serve up "dangerous" methods, but it's up to you to configure your networking so that they are served in a not-dangerous way.

Your upgrade to the latest version will be fine. The note you have found is purely informational, it's just telling you that Atlassian have encrypted some passwords in the new version. The upgrade will handle this for you, there's no need to do anything.

That tells us that your Confluence server is not importing that group from your identity management system. You'll need to talk to your admins about what is imported and why this group is omitted.

No, this error message really is what it says it is. The user running the Jira service on this node does not have the right permissions on the shared storage directories. On a file share, remember that you have to give permissions to both servers - the one mounting the remote storage and the one providing the storage.

Welcome to the Atlassian Community! This happens when you create a new git repository the same as an existing one, but with a README file. The message is telling you that you need to merge rather than try to start again. Do what it says - a git pull will get everything in line for your next push.

You need to go through the support call you raised with them, they don't have a telephone support system.

Ok, so let us turn it around. Why do you think it works better? Not one of my people use Temps because they do not let people work together. How have you solved that?

I didn't really answer the "when I should use them" part of the question. There is a good answer to that - use them when they can convey a message that everyone who might read it will have a similar understanding of the message and to save you writing an explanation. For example. "Here is a picture of my cat being cute".…

Because you had the test issue type to use.

I think it's the smell of the lightning The main one was a holiday in an archipelago, I always associate the holidays we had there with summer. One year, we had been having a glorious summer, I'd read the Lord of the Rings while alternating between a quiet beach and propping up a 16th century fortification in the sun. But…

Typically English - storms. Lightning, thunder and huge amounts of rain. A storm always reminds me of my summer holidays around the UK when I was a kid - they had a knack of turning up at just the wrong time, or being spectacular and hence memorable.

I am not sure what you are trying to do here. Sub-tasks have a single parent issue, they are a part of that one issue. It's nonsense to pretend that they are a part of two separate issues. So there's no logical way to do what you describe.

No, the company managed backlogs are different to the team-managed ones, they are far better for sticking to the process and sharing outside the team.

Again, solve what? There is no problem with Jira defined here. The original post is about doing something the wrong way because the people who built it don't know how Jira works. The other problem we seem to be having is that people are not understanding that deleted issues are deleted. Both of these problems are solved by…

Bother,, yes, missed off the whole point! Thanks @Trudy P Claspill