Nic Brough -Adaptavist- Expert

It's never needed "admin access", just "bulk edit" access in global permissions. (Yes, your admins need to set that, but I'd say 60-80% of Jira systems I've seen allow buld edit to "any logged in user")

The API already returns data in JSON format. If you want to store as JSON, write JSON into a text field. If you want plain text, stored as JSON, you'll need to write a new custom field type that can take input and reformat it as JSON, and return it in a viewable format that you prefer (noting that if that is JSON, the API…

Ignore me, I didn't realise these fields got exported in 8 (I don't export a lot). Thanks for the update @Max Foerster - K15t !

There is no way to do this without code. The Epic Link has a block of dedicated system functions built behind it. You would need to write a new custom field type to support this, including replicating all the functions in Jira Software that are not part of the field but pull it in.

Yes, but there are some complexities you need to think through. It depends on what you mean by "import". If you mean you want to take a 7.6 system, copy it to another database and then upgrade by pointing a 7.13 installation at it, then Jira does support doing that. But it is NOT the recommended upgrade route, and I would…

I'm afraid I'm stuck, with no log and no experience with that app, I can't do much. Have you raised this with the authors (Glintech)?

It looks like one of your admins has added an app to provide these fields, possibly one of the scripting plugins.

Jira fields don't have functions that do that.

It means the call is asking version 2 of the API to fetch data. Atlassian tend to leave a couple of versions of the remote API in place in order to reduce the amount of re-working people have to do as they evolve.

If you want our help, I'm afraid you are going to need to tell us what the problem is. What are you expecting, what happens, and what have you configured?

I don't know - your admins could have configured it away from the default. 

When users are updated, Confluence fires an "event". With some code, you can write a "listener" that can pick up events and act on them. Start at https://developer.atlassian.com/server/confluence/event-listener-module/ - there are also guides to getting started with development in the sidebar.

It would be faster, cheaper and easier to just do all your tracking with email inboxes. If you turn off most of Jira's functions, you don't really have any use for it. I think you need to step back and look again at the actual requirements you have for request tracking. If it really is "just email", just use email inboxes.

What do you mean by "cluster mode"?

It looks to me like your "completed" status is not "done", because it is not in the last column of the board. It needs to be in with the three "cancel" like status to be considered "done". You should be able to go into the column config and drag and drop it into the last column.

You are not going to make Jira look like OTRS - they are designed very differently to do similar things. You can run Jira without any UI, over email only, but you are going to struggle a bit, as you won't have access to most of the more useful stuff - the custom fields, reports and so-on. I would also strongly suggest you…

The training courses are working for me. Have you checked with a different browser, and made sure you are not muting or blocking the sound?

I do not quite understand what you are looking for here. If you put a field in front of a human on a screen, they pretty much know it is there for them to put data into. And Jira fields display their names (and a description if you give them one) as a prompt for the people hitting create or edit. Could you expand on what…

I think you mean you want to grant Jira Software access to a group, so the people in the group can log in and use the Software functions. You do that in "manage applications", where you name the login group(s)

There is a known problem with mail handlers that can't handle incoming email - they can try to create a load of issues from email, fail, and don't create the new issue, but they do increment the project counter. Could it be some broken emails?

It's because the issue statistics gadget is only looking at one field, not two. But, it may also be a broken index. I think you'll need to show us what you think is wrong with your gadgets?

Admin rights don't mean "can do anything". You still have to have the right project permissions. So the first test is to log in as your integration user and see if you can create/update issues in the UI. If you can't then check the project permissions, and if you can, then we need to start questioning what Rapid7 is doing…

The accepted answer still stands as correct!

You will need an automation or scripting app that can provide an automatic "create project as a post function" in your workflow. I've done this for Server a couple of times, but I think we run into permissions problems if you try to do it on Cloud, where the user running the issue through the workflow needs to be an admin…

It means that you (or one of your co-authors) have put a restriction on the page that blocks you from seeing or editing it. You'll need to talk to the person who has done that.

Off the shelf, the installer does that automatically, you just need to give it the connection details. Where are you stuck?

I would very strongly recommend that you do not do this. You should never write anything directly to an Atlassian database while it is running. You will corrupt your data, even if you're using your own tables. Your app should use Active Objects instead - with these, you don't have to think about the database connection,…

Have a look in the table confversion, then look up the highest "buildnumber" on https://developer.atlassian.com/server/confluence/confluence-build-information/

The permissions is the "people who have access". In that tab, you will see a list of people and/or groups who have some access to the space. The administrators are the ones who have a tick in the "administrate space" column.

Yes, the "original estimate" is part of the time-tracking. If you turn off time-tracking, that field has no use, so it goes away. If you want to keep time tracking, but just stop people logging work, change the project permissions so that no-one can log time.