Nic Brough -Adaptavist- Expert

and? What do you want to talk about?

The person who is going to pay the bill only needs to be named as the billing contact for the system (my.atlassian.com is the quickest place to see who are the billing and technical contacts for your Atlassian systems). They do not need to be granted any admin rights, or even any access to your Atlassian systems.

A snippet of error with no context is not a useful way to ask a question. We can tell you from that that you have a network problem or a service is down, but nothing more. Please, ask your question properly.

What error do you get when you click there?

Greenhopper went away over a decade ago, and it never had any of the calls you suggest. Try looking for the Jira Software REST API which replaced it.

Please re-read the last paragraph of my last comment.

A Jira system with no issue types cannot be used. It can't be. With no issue types, there is nowhere to configure how issues work, let alone create an issue. As you pointed out yourself, you said you were getting the error the original poster is getting. The one that tells you that you can't delete the last remaining issue…

> I didn't have any idea such a powerful product as Jira may have such stupid restrictions. A restriction that stops you from making the whole thing unusable? I do not think that is unreasonable. >I also had no idea about some "types schemes" - to me they look supe-, over-complicated. What happens after I create another…

"This is exactly the problem. I can't delete this "test" type because of the error that the topic starter described" Why are you trying to delete the last issue type available? You can't have a system that works without at least one type.

Yes, but you may have installed an upgrade that does not work. The error message you are getting is very generic and you've only given us a tiny bit of the actual error - it's worth looking down your logs for the rest of the error, as it will probably give you a class name that you can identify the app from. There's no way…

Oh, I see now. You can't edit the default issue type scheme, Jira needs somewhere to keep all the issue types in a global list. In the admin menu, go to the line above for just "issue types" - you'll need to delete the issue type you don't want from there. That will remove it from the default scheme as well.

Sorry, I miskeyed that. I mean just app - apps are what Atlassian markets plugins and other add-ons for Jira as nowadays (they use "application" to describe Jira Software, JSM, Confluence, Jira Core etc) To fix your workflow post-function failure, you need to install a version of the app that provides it that is working…

Get a version of the appl that provides the post-function that works for your version of Jira

It doesn't matter which is more up-to-date. The APIs are for different things.

But what are you trying to do and what are the responses from the software?

Welcome to the Atlassian Community! One of the points of using Software as a Service is that you should not have to worry about backing it up. That's why there's nothing in the core product to give you a backup - you don't need them. I have to ask the question of what you want to do with these backups? To take a manual…

You have not told us what is wrong or what you are doing, so we can't tell you what you need to fix or do differently.

Welcome to the Atlassian Community! What do you mean by "locked"? Is it just that the screen you are on is not responding while the import is running?

Team managed projects can only have one issue type at the Epic level.

The only way to do that would be to remove the gadgets that are showing the links to things your people can see. I'm not that a dashboard without links is of much use to people.

No, you're not looking at the issue type scheme, you're looking at the list of schemes. You need to go in to edit the scheme you want to change.

This means you are not looking at the issue type scheme in admin. Please go to admin -> issue type scheme and edit the one your project is using.

The box you have in your screenshot is just one part of the page you are on. To one side of it, there is another box that looks the same, but has different issue types list.

Welcome to the Atlassian Community! You are assuming accounts work in a certain (traditional) way, but things have changed a little bit. The older way to handle accounts is that a system has a list of people, with unique identifiers for them, and a human would log in to that system with that account. We have moved on from…

Click an drag the ones you don't want into the other pane, and drag in in the ones you do want to use.

On what? The information above is accurate.

Welcome to the Atlassian Community! This is an error message that used to be thrown by some old versions of Jira Server/DC when people had created select list options with silly names (humans expect to see proper words as option names, like red, green and blue, not badly half-coded things like [red], {green}, and -blue-).…

The first problem you list is caused by the your action in the second problem. You have told Jira to run scriptrunner functions on a transition, but because you have disabled the app, it can't run them. To fix the first two, you need to enable Scriptrunner, or remove all the calls you are making for it in your workflow.…

You do not do this in a post-function. Post-functions run at the end of a transition, after you've decided you're going to commit to it, it is too late to change your mind about doing it. Imagine you're going sky-diving - a post-function would be "open parachute" as you're on your way down, not "decide not to jump". You…

Welcome to the Atlassian Community! Yes, you can do this. How, I can't tell you, because you have not said what you are trying to achieve. Bienvenue dans la communauté Atlassian ! Oui, vous pouvez le faire. Comment, je ne peux pas vous dire, parce que vous n'avez pas dit ce que vous essayez de réaliser.