Nic Brough -Adaptavist- Expert

You could try to build one, but you'll find it hideously complex, and hence, probably inaccurate. Why do you think you need to do this?

It is not clear what your question is about. What are you trying to do? On the authorisation side though, the simple answer is use Oauth, as per docs.

The connection problems you are having have two possible root causes: * Servers are not responding - check https://status.atlassian.com/ for updates on that * Your network connection to the servers is failing - you'll need to look at your network for debugging that (As an aside, Jira Cloud is not a PaaS solution, it's SaaS…

You could turn off the whole lot by disabling the plugin that provides it, but you would lose all of the other functions. I would check the system plugins list, find the DVCS one, then see if there are function related modules you can disable (from memory, there are not, it's all or nothing, but it's worth checking as my…

FWIW they are indeed Epics - this is a "teams in space" system that Atlassian uses as an example data set for docs and demos (and, provides to partners for the same, so we tend to have a few copies lying around and recognise the baseline data in it)

I'm afraid we are an Atlassian community, not an Oracle one. Some of us might be able to help, but I don't want you to be left hanging here - there's little chance this community will respond. You may want to ask the question in an Oracle forum, rather than an Atlassian one.

That does not make sense - you want to reopen an issue when you close or resolve it? If you really do mean that, then the thing to do is edit your workflow such that you have transitions called "close" and "resolve" that go back to one of the open status. This will not make any sense to your users though. I very strongly…

There is no context given in your question - for most of us, you need to frame it by explaining what you are trying to do, what you mean by "storage document" and "namespaces", and explain why you're not using the REST API as documented

I've been a bit dismissive there. I do know CSV is the greatest common divisor in the cases of a big table of data, and so it's going to work almost everywhere. There is absolutely nothing wrong with that. I think what I was trying to get at was "use a massive CSV pile to get you started, then look at other, better,…

I cannot think of a way to get close without some significant coding, and even then, I trip up on one part of it, as I am really not sure it could be done without hacks to the core code (which you could only really achieve on Server/DC installs anyway) TLDR: there's a lot to think about here, some tech, some procedural.…

They apply to the wissue type. A board is a view of a selection of issues, it can't change the workflow just because it chooses not to display parts of it. The status in the workflow are valid for the issue, so the workflow has to allow you to use them, irrespective of what the board is showing.

I'm afraid it's a bit more complex that the SQL you've generated here. And it's even harder because you cannot search for a negative - people who do not have access may not be in your database in a way you can recognise or report on. Take your "can not log in" - what application access does that person have? The 1 means a…

Ok, it's a bit weak keeping stuff in CSV in general, but for a one-off "getting started" run, that's perfectly normal. Start at https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/ - it should not be hard to re-shape your CSV into something Jira can read, you're probably 95% of the way…

I'm still not sure why you looked at 1433 (you already said Jira was connected to Postgres), but I'm glad you got the http working on 8080 You don't need to think about jira.exe - that's not running here, Jira is a web-application that runs on Tomcat. But it's working, so this is not causing you problems and doesn't…

It's a bit buried, but go to id.atlassian.com, click on your profile icon, to get a menu option for "account settings". In there, hit "account preferences" and you'll find "delete account"

To limit the status available to the ones you are using in a board, you will have to remove all the ones you do not want from the workflow. i.e. make the board cover all of your workflow. You can do that with simplified workflows, yes.

Yeah, I'm afraid that's not what sub-tasks or sprints are for.

Ok, great. Again, I'm really sorry I was so unclear. The Sprint field in Jira Software does not apply to sub-tasks. The logic is good - sub-tasks are a part of their parent issue, not independent entities, and hence they are only "in a sprint" by virtue of their parent being in it. Technically here, the sprint field is of…

Include and all the other stuff that grabs data from other places

That page is being generated from (real) Confluence content and presented through K15t's Scroll Viewport - You'll need an app that can extract and translate Confluence like that does.

Jira has a bit of a confused approach to settings. One the one hand, we've got every admin on the planet yelling "keep it simple, share config, keep your processes consistent or you will make a mess" and then a load of process people yelling "let everyone do whatever they like and run their projects however they like" So…

It's not as easy as it sounds. The underlying core data structure in Jira does not quite support it and the ability to do that was not seen as important enough by Atlassian. Hence others have gone and created (server) apps to do it. There's a couple of requests for it to be built into Cloud, but they're really not seeing a…

You put a sub-task in a sprint by placing its parent issue in the sprint. Sub-tasks are a part of an issue, not separate stories in their own right, and hence can only be part of a sprint by virtue of their parent being in it.

Jira doesn't have anything deeper than the cascading select. You will need to look to multi-level-cascading select apps. However, I do not think there are any for Cloud yet.

There does not appear to be anything wrong for any of the Trello accounts I've got access to. There was an incident yesterday that took Trello offline for a lot of us, and very slow/unusable for others, but it was fixed. So I suspect the problem is local to your Trello space or something on your computer or network. Are…

So, first, you need to enable the function in the requests - https://community.atlassian.com/t5/Jira-Service-Management/How-to-allow-customer-close-reopen-issue/qaq-p/67487 has a set of good screenshots on that and some troubleshooting when people get stuck. The second part of it I am less sure about. You can edit outgoing…

You don't. Remember that sub-tasks are a part of their parent issue, not an independent issue in their own right. They can't take on ranks that would take them outside the rank of their parent. It does not make sense to rank them outside the context of their parent issue, so when you remove those from your display, there's…

Atlassian generally do not build stuff their partners app suppliers have built until it becomes something that they see as being important as part of the core product. I suspect "project fields" are something that's not seen as important as a lot of other stuff in their backlog, and is also easily solved with ProFields. So…

Sorry, I was totally unclear on this. Jira Software comes with a Sprint field built into it. This appears as a "custom field" but my question was if you have added your own Sprint field. And I did not explain that there was a difference. Could you take another look at the list of custom fields? Do you have one or two or…

You will need to amend your workflow. The workflow for the issues define what status are available. Your boards are a view of a set of issues, and they have no option but to show your workflow, otherwise they would be useless. If you want to stop status X being available to push the issue into, you need to remove the…