Nic Brough -Adaptavist- Expert

You would need to find or write an app to do that, and you'll need to think very carefully about how can keep the two in full sync. Conflluence already has versioning built-in, there's no need to try to wedge it into another source control system. In the other direction, yes, yout git can create pages and update them, over…

You would not need the .getName()

Welcome to the Atlassian Community! No, it will be fine. Licences do not look at the start date, only the expiry date - you can apply the key for your renewed licence any time.

The JQL is as simple as "<custom field name> = <name of value>" for a select list. You could be more clever with "<custom field name> in (<name of value 1>, <name of value 2>,etc)" As you type the JQL, it will try to help you autocomplete, when you start typing the name of a field or a value.

We can't really help you - we have less access to your systems than you do. You will need to talk to your application administrators, they need to alter your groups, roles, or the project permissions.

Welcome to the Atlassian Community! What do you get as a result from the "apt-get install git" command?

Welcome to the Atlassian Community! Port 22 is the default for SSH, but you can't connect to Cloud systems with SSH to get a command line, they're designed to be used interactively or with git SSH.

Welcome to the Atlassian Community! The short answer is "you can't". App vendors can code however they like and if that code breaks someone else's app, there's no way to stop that. You either need to stop using their app, or code yours so that there is no conflict.

That means there is no way to get any information on people logging out, because most of them will not. Humans tend to just close the browser window, or just not use it, we rarely log out of a system. I think you have a problem with micromanagement here, not a data problem.

I am sorry that the answer you got before was misleading - it was generated by an AI that has no understanding of your question or Atlassian software. Projects are not really locked to a type like this - the Scrum, Kanban, and other project types are templates. You chose one when you create the project, and it creates all…

Welcome to the Atlassian Community! No, the abusers only have your email address. If you don't engage with them in any way, then that's all they will ever have. You didn't need to delete the account or change any details (although I would always recommend a password change if you ever have any doubts, or have not changed…

No, that's not the right table. People should use the script registry.

Welcome to the Atlassian Community! Database queries are the worst possible thing to try with Atlassian software - the databases simply are not designed for reporting (it's even possible to take down an Atlassian database sever with poorly built SQL, as the data is so not structured for it) You have not defined what you…

It is indeed rare to see a sprint where completion exactly matches the estimates, but the whole point is that you are measuring and reflecting on it. If a team repeatedly rolls issues over to the next sprint, then you can consider them as failing. Exactly where they are failing is a huge point of being Agile - they need to…

Welcome to the Atlassian Community! System administration is something your Cloud support people have, it's not for end-users. Why do you think you want it? Have you raised a support call with Atlassian to report what the problem is?

Welcome to the Atlassian Community! Atlassian accounts cannot use the same email address, and if you've managed to somehow duplicate an account with the same email address, then the Cloud systems are simply picking up the first one they find when searching for your account This is something inherited from server - you can…

Why can't you filter for company managed projects? Are you not logged into Jira? The only way to stop someone filtering for issues is if you remove their permission to see issues entirely, and even that does not stop people creating, running, and then using filters in dashboards. Can you explain the problem a bit more?

The simple answer is "do scrum properly". Pick a pile of well-understood stories that can be dealt with during a sprint, tell people you are going to deal with them, and then deliver them. When you fail to deliver what you committed to, look at how you could improve. If you end up with time left over, great, the team can…

How are you forcing log out? (Probably a more relevant question, to my mind as a consultant - why are you thinking micromanagement is a good thing?)

You can't retain issue keys unless they * match the issue key rule for the projects you are importing into * are ordered in your import file such that as Jira reads them, it will create them in the right order It doesn't really retain the keys, at all. Jira will simply create the issues in the order it reads them and hence…

Welcome to the Atlassian Community! Why are you thinking you want to install issue tracking apps in a wiki system?

@Meg C Welcome to the Atlassian Community! There is no "solution" beyond what I posted before. You have to create your import file in a specific order and fill in any blanks, and accept that importing into a project means that you have to have issue keys that match the project-sequence that Jira works with.

I remember the days when it did work that way. I don't think Atlassian are ever going to go back to that. You will need to raise this with support if you want to get Atlassian to pay any attention to it, the Community is not a place that they look to for suggested change, not unless a lot of us show huge interest in an…

Welcome to the Atlassian Community! You have tagged this with Cloud, but Cloud licencing doesn't work on "expiry", it's a subscription model, so unless your "expiry" means "it's stopped working because we haven't paid the bill", I suspect you are actually on Server. Whatever system you are on,…

The best option is probably to set up the new issue type in the target Cloud system, making sure it has all the same fields and status in their workflows as the existing issues in the old system. A second option would be to move all your issues to the desired issue type in your existing system. This could be a bit of a…

The docs @Florian Bonniec has linked to are for the latest version of server, and the Cloud version is pretty much the same. You need to edit the board filter, putting the order in there. You can get to the filter quickly by clicking "board settings" and looking at the general tab (which is the default). The clause is at…

Short answer is "no". It's a breach of contract for people to publish the contents of the exam, and if you do so, you lose your certification and access to all Atlassian stuff. You can only (re)publish the questions and answers that are in the sample documentation, as they're already public.

>Don't bring a story into a sprint if you don't think you can deliver. That sounds like a madness to me. I am sorry that this is going to seem rude, but I really don't think you have understood what Scrum is for. (Or Kanban, or even Agile in general). It's about delivery. You say "we think we can deliver X" and then you…

Simple - be honest about it. Do not bring the story into the sprint if you don't think you can deliver. Again, you should not be drawing stories 2 and 4 into a sprint. If you can't complete them, do not tell your users that you will, you're lying and you're not Agile. Issues going into the next sprint is a direct…

The whole point of Scrum is that you deliver something useful or at least testable at the end of the sprint, showing the end-user that you are progressing. This is well-aligned with Agile - it also focusses on delivery over planning, and looks for iteration - if needs change, it can adapt. It is not Agile to promise you…