Nic Brough -Adaptavist- Expert

No. One of the big points about git is that it is built for working on remote repositories. It doesn't work unless the users have local access to the code and that means a copy of it. And of course, once someone has a copy of something they can do what they want with it.

Not any more, the app has been absorbed into premium entirely.

For 1.8m tests, I'm guessing you probably should be on Data Center rather than Server. https://marketplace.atlassian.com/apps/1210725/data-generator-for-jira?tab=overview&hosting=server is what I've used on Server. It probably works ok for Data Center, despite not being flagged as valid.

Are there more errors further down? Jira does tend to throw out a lot of them as they cascade through the code and it's usually the last one that is the most useful. It is looking like there's a problem with a field or app function rendering, but we'd need to see the rest of the errors to be sure.

It's also in the system info page (along with a load of other stuff you are probably interested in if you are interested in whether it's DC or Server)

Assuming by "unmanaged accounts", you mean an Atlassian account that has not been claimed by a organisational domain for inclusion in their licences, then yes, people can delete their own Atlassian accounts. If they go to id.atlassian.com and go through the options, there is a delete link in the security or preferences…

Check each one for the "fix version", and upgrade to (at least) the lowest version that fixes them all.

Only admins can create company managed projects, they're intended to be controlled by the organisation, and people shouldn't be free to just randomly create projects. You should really only have 3-4 administrators and part of their role is to create projects when they're needed. Project creation doesn't take too long if…

Is this person acting as a customer or as a developer when you include them in the request? Do they need to see the issue or the request?

People get sent emails about resetting passwords when you add them or they request a reset. Crowd has no way to know that you're adding users who aren't going to use it!

Log in with the more advanced (and hence more secure) methods now available?

To get into a conversation with Atlassian support on a human level, you are going to need to raise support requests. It might be easier to ask the Community here though (I'm told there's 3 million of us, vs a few thousand Atlassians, most of whom do not do support!) However, I am sorry, but none of your questions give us…

I really want to say that I was not trying to teach anything about boolean logic to you here. You had that nailed, but not quite which particular rule-set Jira's JQL subscribes to. Although to be totally Boolean, there is only one right way to interpret the rules (which we all did here) Annoyingly, it does feel like Jira's…

I don't think you will ever see "destroy what the human wrote and build something useless to them" implemented. An issue summary probably should be a short bit of text that explains why we are raising an issue. Encoding other stuff into it, defaulting things that people will then ignore - not helpful.

Yes, the docs do say that. Do you have a question about it? Are you stuck somewhere?

Could you expand a little on your TLAs? I'm not sure people will give you a helpful answer without knowing what they are (we might answer the wrong question)

Ok, the easy bit is obviously just to change the "set issue type id" to create an issue instead of a sub-task type. Then instead of the sub-task linking, you can have a look through https://library.adaptavist.com/entity/add-or-update-the-issue-link-for-an-issue-in-jira to see how to work with issue-links.

That's not in the to-do column, it's a swim-lane header - it's a bit misleading in this view that the text fits under the column heading, but the white bar with the VIS-15 issue in it actually goes across the whole screen (all three columns) When you set "swimlanes by story", it will put stories (and of course sub-tasks)…

Creating a new board does not create a new project. Not when done from within a (company managed) project - you click the boards drop-down in the left-hand panel and "create board" appears at the bottom of the pop-up menu. >Company managed projects should allow an Admin to control what fields and workflows projects use but…

There's no way to remove the roles from the projects, the roles are globally available. Standard advice is to keep the list of roles minimal and generic (doesn't matter too much if you call someone in a Scrum project or a Waterfall project a developer. Most scrum-masters don't mind being called "team leads") I am not sure…

Log into an Atlassian system and go to the id management link and find the account preferences under there. Or, in most cases you can use https://id.atlassian.com/manage-profile/account-preferences for a direct link. There's a "delete account" link on that screen.

I don't know that there is. Can MS Forms be told to export in the right format? If not, then no, I'm afraid you'll need to work on something that might automate getting the format right for import.

I think you may have landed in the wrong place. This is a community of people here to talk about Atlassian stuff, not printers or windows. My guess is that your printer supplier or internal helpdesk is using Atlassian to support the documentation or helpdesk and you have clicked on "help with Atlassian system" instead of…

The schemes don't control the Scrum functionality, but if you choose to share the schemes across projects, the new project process doesn't go through all the stuff you need to make a project look like a Scrum project. Main thing is that it won't create a scrum board for you when you create the project, but that's easily…

Not that I have seen! Sorry!

Great, those are quite easy to populate - see https://library.adaptavist.com/entity/update-the-value-of-custom-fields-through-the-script-console for an example of doing it in the console (it'll translate straight into a listener)

Then you'll need to go into the app and change the url in there.

This is what it says it is. A board is a view of a selection of issues, which it does by using a filter. The new issue you are creating does not match the board filter, so the board is not selecting it. You mention assignee, so an example might be that your board is selecting "Project = XYZ, and assignee in (Alice, Bob…

Yes, Big Picture is a simple "install it and start using it" implementation. You don't need any skills to use it beyond general knowledge of how to use a computer, and some understanding of how your organisation is organising the issues in Jira and hence Big Picture.

No, you need to connect your Active Directory/LDAP/IDP/etc. If that happens to be on Azure, then you'll be connecting Azure to it, yes. This will all be done through Atlassian Access.