Nic Brough -Adaptavist- Expert

You will need to create a dummy user that has the email address of the group.

Yes, this was a problem last week, Atlassian say they've fixed it.

What type of field is it, and what is the searcher for it?

What do you mean by "query all existing link types and names for an end user"? Links are between issues, they have nothing to do with users (beyond people being able to use them)

Not system priorities - they are global on Cloud. You would have to create a custom field if you want different priorities by project

Talk to your admins - they need to check the notification scheme to make sure it is set up to send you notifications.

To start to debug this: * Identify a single issue to work with - one where the owner field is clearly not empty when you look at the issue in the issue view * Run another search that will include this issue for some other reason along with another couple of issues. Add the "owner" field to the issue navigator to check if…

What do you mean by "dev status api of Jira"? Again, this is not an error message Jira generates, it's coming from somewhere else. You'll need to work out what is generating that error

How are you putting the time to response field into the email?

For a Kanban story, the required "attributes" are * a description of what needs doing, so someone can do it (this can be as simple as the summary field), * a status, so that everyone knows where it is in the process * a single assignee, so that everyone knows who is responsible for getting it done (should be entered at "we…

I think this is "solvable", but not by trying to do it with the software. The computers should be trying to help you, not get in the way. Jira can very easily set up to be complex, but when people do that, it's a symptom of them not working together well, not bad software (and there's a lot of other software we can all…

There are apps in the Atlassian marketplace that can throw Jira data out in all sorts of formats, many with clever formatting and processing on top. I tend to work in Jira and hence simply don't use them, so I do not feel qualified to talk about them. You might also find some stuff on the other end - MS forums looking at…

Jiraissue, issuelink, nodeassociation and half the AO tables related to Advanced Roadmaps or the ones related to Structure or however else you have done features and initiatives. It really is a mess in there, you are using the single worst possible way to approach it.

I don't tend to code in Word much, moved on to using Confluence for all my docs years ago. A search for "vbscript rest" should find you vb coding help, which you can combine with https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/ to set up a pull from Jira.

This usually happens when you're trying to use an external user directory and haven't got the config quite right. Have a look through https://confluence.atlassian.com/bamkb/could-not-login-admin-user-after-admin-account-creation-at-setup-740001920.html to see if that's what's happening here

They won't just host some random app. You'd need to get it added to the Atlassian family of apps if you want them to host it (unless it's an app that can run entirely on the Cloud app framework without needing other servers) Could you explain roughly what you have done and why you think you want someone to host it for you?…

Sourcetree is not a deployment or ci/cd tool, it's a source viewer and manager. You could probably get something done where a commit triggers a build and deployment, but all of that work would not be done by Sourcetree or Bitbucket. I'd strongly recommend getting a ci/cd tool to do the build and deploy. If you were on…

You don't need to add the new record, it's now confused it into thinking you are verified at the same time as not. Remove the DNS record and talk to the people who originally verified the original domain.

No, as I said already, workflow functions will not affect indexing. They only get run when you are using a transition.

What do you mean by "digi accordion"?

The one referred to on the download page. The closest Atlassian get to an "unstable" version is the "early access" releases, available from a different download page.

You cannot do this. If an issue cannot be seen by a user, then it is not just not visible to view, but its data will not be returned at all when a filter is run, so it won't feed into any reporting done with the filter. Imagine for example you have three issues with a number field populated - AAA-1 with 2, BBB-2 with 4 and…

Did you re-index after changing the searcher?

I am not sure what you are looking for here? Your domain has already been verified, you should talk to the admins of your systems to get password policies changed.

No, Jira Software calculates velocity, you don't need Advanced Roadmaps to calculate it. For capacity allocation, you have to actually go through a couple of sprints, essentially guessing at the first one and then using the results to refine your estimation and capacity to something more realistic than a guess. You…

Yes, you do need to go through each version I listed. 6.0 to 7.0 almost always fails, so get it to 6.3 or 6.4 before going to 7.0 You must not skip 7.0 or you will end up with broken data that you won't find out about until you get to 7.8 or above. 7.13 is a bit flexible, you just need to be on 7.6 or above. 7.5 and lower…

No! Do not skip most of these versions, you will break it if you do. You must go through the versions I listed before in my answer, although obviously, if you're on a later version than 6.0 you won't need to go back and downgrade. 

Ok, but you have made an incorrect assumption here. You are assuming that SQL is run to get the underlying data for a report. It is not. Reports do not run any SQL generally, they get their data from the index, which is not SQL based. You will need to write your own report as an app.

Can't see the videos, but from your description, I know something similar can happen when you have a misbehaving plugin installed in firefox. I'd want to test with another browser, or firefox in "safe mode" with all plugins disabled.

It's updated as often as Atlassian releases new stuff it needs to support. This can be as frequently as 2 weeks. However, they do not remove anything from it without making it a completely new release. If you were using calls against the version 2 REST API from the day it arrived, then those calls will continue to work the…