Nic Brough -Adaptavist- Expert

How are you creating this "custom report chart"?

You say "I want to use jira server with simple domain (mean with abc.mydomain.com ) not want use like "/jira". But reset other jira application want to use like abc.mydomain.com/servicedesk & abc.mydomain.com/confluence. " You simply cannot do that (without doing some coding). As I said already, if you serve an application…

This message means that the account you are trying to add has been shut down, almost certainly as a result of the owner saying "I don't want my Atlassian account any more, please close it" You'll need to get the owner of the account to re-enable the account, or create a new one and let you know what that is so you can add…

Not natively, Jira has a single create button because there could be thousands of project/type combinations someone mighe want to create and it really does have to ask. However, with some code, adding your own buttons is quite easy. You'll need to find or write something that can add a "web fragment" - these are objects…

If you are using a Classic project, then you can use JQL for swimlanes ("Job Title = xyz"). Next-gen project boards have a fixed set of Group-by options, no JQL options (yet)

There's no built-in way to do this. Currently, to do it in full, you'd need to download both systems, merge them on server and then upload that to the target Cloud system (which destroys what was there before) I would look to use 3rd party migration tools to do this. A blatant plug for Adaptavist here, but…

You haven't given us the error message.

Jira doesn't have any "field visibility" functions, so there's nothing automation could do.

Yeah, this is one of many reasons you should not be reading the database. It's absolutely the worst way to get data out of Jira. You're going to need to construct a lot more SQL - you need to read the custonfield table to establish what type of field it is, and then conditionally read one of the olther columns for the data…

You need to set the resolution to something (absolutely any value - the system sees an empty field in the database as "unresolved" and then "resolved" if there is any content) You'll need to take a look at your workflow. Look at what status you consider "closed", and then look at all transitions into those closed-status.…

It is the worst way they can possibly try to report on Jira. Your user team needs to be told that, and told to stop trying to do things the wrong way. You should not allow them any access to the database. More to the point, yes, you are correct. You should never create views, functions or new tables. You are unsupported…

Atlassian do not seem to have any plans to do this at present.

I would guess that your changes mean that you have reconfigured things such that your status are not "done" when you expect them to be. Jira works off the llast column on the board, is that not how it is working for you?

One of your admins deleted the field that had those IDs. You should reconfigure the projects and boards to use another field that still exists. Note - those old fields may well have been named "Story Points", but they were just simple numeric fields. I suspect your admin might have been doing the right thing - getting rid…

Cloud has an end-user backup system that allows you to grab a copy of the whole thing once every two days. There is no "project backup", it's the whole system. If you're not using that, then there is nothing that can be done. Issue deletion really iss issue deletion, they're gone. (I always recommend removing any "delete…

I do not think you have a "number" field. It looks to me like you have created a select list field. How are you trying to do the sort in the search? (Click or order by clause?)

No, the post-function only acts when a transition is executed.

Bear in mind that can only actually work if the issue types have exactly the same configuration

No, that's the opposite of what I said. 

the estimate you made for it.

It is what it says on the tin! Every status belongs to one of four groups; to do, in progress, done and no category (try to avoid that one) The statusCategoryChangedDate is simply the last time the issue moved from a status in one category to a status in another.

Are all the sub-tasks in the last column on the board?

Not the "friendly name" - the friendly name of a page is always derived from the page's title. Change the title, change the url. But Confluence pages do have a fixed id and the url that you get if you do include special characters in a title will work for it because it is based on the id, and if you look in the page…

In theory, you could do this, but the cost of adding all the apps you'd need to even begin to replicate Jira Service Management's workflows, fields, notifications, reporting and so-on would probably rapidly add up to a lot more than the cost of your current Service Desk. Not to mention all the work building it.

You don't. There's no information in your import which would be able to tell it which domain to choose for each new user it needs to create.

No, to get Advanced Roadmaps, you have to go to premium. It's no longer "just an app".

Of course it will, you're adding Software to a site that does not have it. Software is an application that adds functions to Jira. So you'll see new stuff in your existing site. However, it won't change your data, just make new stuff available.

 I want to question why you think you want to give anyone access to the views? Of what use is it?

Because the work is being done on the sub-tasks. You don't want to double-log work on a sub-task and its parent. The estimates and work logged are summed up for display and reporting though. Go to the parent issue and look at the estimate area - you will see a flag for "include sub-tasks". Let's imagine a really simple…

aaa.atlassian.net is a totally separate instance to bbb.atlassian.net. Ok, there's shared infrastructure that you don't need to care about as it's a service, and if you create them from the same account, they'll be managed together by that account, but you should think of them as totally separate and independent, at least…