Nic Brough -Adaptavist- Expert

If you don't have error logs in Jira, then the problem is almost certainly going to be that the call never made it to Jira You'll need to look at the external application to see what it is logging. What is the response back from Jira when it tries to create?

Where are you trying to use it? (What's the language and call to Jira you are making?)

Your second point really resonates with me and, I suspect a lot of other people. I went to Atlassian Open in Vienna and saw that "stop changing things without letting us plan for/adapt to it" was the third most popular improvement request on Cloud. I've also worked with a team that did some training on Cloud on a Thursday…

Ah, that's not because it's a space page, it's because it's a page that existed before the new editor was installed on your instance. Existing pages will continue to use the old editor, with sections. New pages will be created and edited with the new thing, layouts. You've reminded me to dig up…

I'm sorry, I forget that the new editor has removed the functions for moving sections up and down. Sections have effectively gone away on Cloud. What you get now is "layouts" which are "simplified" down from sections. Annoyingly, you can't move them around any more as they're not really sections. You have to insert things…

What would you ask Atlassian to do to persuade you to stay with it?

Ok, merging is complicated. See https://confluence.atlassian.com/jirakb/merge-multiple-instances-of-jira-cloud-779160767.html to get started.

The first screenshot shows a layout bar that is hidden until you toggle it on with the button that is highlighted in solid blue - the highlight is there when that menu is shown, the button is a toggle. In the second screenshot, the highlight is not there, so you have not clicked it to show the layout bar (so the bar…

Use another function that does the job. We can't tell you much more unless you explain what the problem is.

Thank you, it really is great to get a well-considered and absolutely clear answer to "we are not sure what you mean". You could try changing the language or translations, but I would start by asking why there is a need to change it? What would you like to change it to, and what is the problem with the current wording? (To…

The version-picker is a built-in custom field type that picks from the version list. This only answers your question for versions. And the user and group fields too. There are no other custom fields that work from a global list.

What does the atlassian log say?

Is this a simple "move Server to Cloud" or are you trying to merge from Server on to Cloud?

The transition "planner close" is either not set up as a route out of the current status, or there is a condition on it that blocks you from it. Have a look at the current status and the workflow diagram and check that there is a transition out (or that "planner close" is a global transition with "all" on it). If it does…

I think you might want to ask this in a MySQL forum, as you've not explained anything about how your question might relate to Atlassian stuff (which is what our community is for)

Jira does not have fields like this natively. The table grid editor app is the closest thing I have seen.

I agree too, with all three comments above. The reason Jira is refusing to delete them is that they are associated with data that matters. If you absolutely must delete a user instead of just deactivating them, then you must move their responsibilities first.

It looks like you have not clicked the "layout" button on the child page editor. It is hidden by default. Note the blue highlight around the button on the first screenshot, and that it is not highlighted on the second.

You can raise a request with Atlassian support ( https://support.atlassian.com/contact ) and they will change the url to another <something>.atlassian.net for you. Obviously, they won't do it many times, so make a good choice when choosing your new <something>. They are working on providing urls that do not have to end…

This probably is what it says it is - there are files and/or directories missing from the disk. Have a look in the Admin -> System info page to see what your "Jira Home" directory is, if you don't already know, then log into the server and check that in that directory, there is a "caches" directory. If there is not, then…

Pages are separate entities. If you create one page as a copy of another, you don't want the history of the original, it's got nothing to do with your new page.

They are never going to implement "wedge random numbers in instead of reporting on the actual data". This is more of a human problem. You either need people to put the right data in, or come up with a way to allow for the variations. I described "create an issue for the missing 25%" as "clunky", but it's a better option.

If you need help with this, please share * The board filter * The column configuration for the board * The workflow diagram(s) * A list of issues - ideally, we want to see at least two, one that appears and one that does not, showing status, resolution, issue type and parent issue (where appropriate), plus any other field…

No, Scrum and Kanban boards both work fine with simplified workflows.

The only way to do it is to set up that user so that they can not see the issues that you do not want them to be mentioned on. (Permissions, disabling the account, security levels, etc)

You'll need to copy your post-function scripts over into listener scripts that catch the "move issue" events.

Could you explain what you mean by "statistic type name" in more detail? Perhaps a screen shot?

Yes, I have no doubt you are. I can't tell you more than that. You have told us that you are facing an error doing this, and we believe that you are. But without any information on what the error(s) might be, we cannot tell you more than "Yes, you have an error" An analogy: You want to drive to another city. Your car has…

You're right about the commercial side. Some vendors struggled for years to try to provide clustering in Jira and consistently ran into "it does not work" for four big consistent blocking reasons. (I can only remember two reliably - sessions and shared storage being too slow for some of the non-database data stores), and…

Yes, and yes. You can use any numeric field to estimate and hence burn down. And you can burn down on any status you want. To burn down on status, put the status in the last column on your board.