Nic Brough -Adaptavist- Expert

You will need to talk to the owners/admins of that system. We can't help you with that - we're a community of Atlassian software users who have less knowledge about that instance than you do.

>how can I create an access token in rest API after receiving the request from you You will need to use the method detailed in the REST API docs. However, there's a far better description of what you need to do in Andrew's answer over at…

If it is offering a security level to select, then you have "set security" permission, and you are a member of each level you see.

Have you read the main sentence in the error message? That tells you exactly what is wrong.

Duplicate of https://community.atlassian.com/t5/New-to-Jira-questions/Need-Bepa-tool-access/qaq-p/1373904

To do what you have described above, you will need who to decide who to log in as, and use that account to make the REST calls.

I think you are missing the point - we, the community, have less access to that tool than you do. We're a global community, not your owners or admins. We have no idea if anyone else who uses that system is active here. You need to talk to the owners or admins of that system. We can't know who they are. You will need to ask…

Imagine your issue is a castle, or a factory or an airport. Changing the issue type is akin to saying "I want to convert this building to another purpose, so we're going to need to dig up all the foundations and put down new ones to suit it". The foundations are the issue-type. The user experience is about as simple as it…

We're a community of people who use Atlassian stuff. Most (probably all except you) have no idea what your Bepa tool is. You'll need to talk to the admins of this Bepa tool.

You need to decide who to log in as, and use that account (you'll lose the informaiton about who is raising it, of course, but at least you'll get something) Your JSession is useless unless you've got SSO enabled.

But a text-field based pie chart cannot do anything other than "one slice per issue". By definition, every chunk of text is different. I don't see any use for a pie chart with that.

Could you explain what this has to do with Jira (or even Atlassian)?

Plain Jira (Jira Core) and Jira Service Desk have a simple hierarchy of Issue -> Sub-task Jira Software promotes the Epic type so we get Epic -> Issue -> Sub-task Portfolio for Jira can add Themes and Initiatives and the Structure App can add layers all over the place. (Of course, you'll need to do a bit of config on those…

Then what do you present to people who have not selected a dashboard yet? And what do you replace the login and default screens with? What problem are you trying to solve by making the System Dashboard private?

It's not a "small tweak" in the back end. The issue type is structural, a lot of configuration is hung off it - it determines the workflow and fields for each issue (with the project covering the rest of the config), so Jira has to check that any change of issue type is not going to mangle the data.

No, because it does not make sense to have sub-tasks in a different project to their parent. And the problems presented by different permissions just become impossible.

Yes, that's right. In a purely technical sense, Time Tracking is a "field", as far as it's "a single object that goes on a screen", but the code behind it is not simple, either on how it is calculated, stored or rendered. And it's just a field, it is not a field type. So you can't have more than one of it.

For some reason I've never got to the bottom of, Safari seems to thing /E is a control character and sends something JQL can't handle instead of the plain string. Best I can do is tell you to avoid slashes (and brackets) in the names of options where possible.

The process for updating or adding to a Jira database with SQL is, at an absolute minimum: * Stop Jira * Backup the database * Restore the backup to a (temporary) test installation * Test the copy to ensure that you have a good backup * Make your SQL changes * Restart Jira * Run a full locking re-index (there are some…

I have no idea, I'm an Atlassian nerd, I know less about Jenkins forums than you do. You should be talking to the Jenkins community, not the Atlassian one, there's far fewer Jenkins experts here than you'll find in Jenkins fora.

On Cloud, as you've told us you are running, it doesn't matter, because you can't get to the database. On Server/DC systems, it's a custom field and numeric, so it's in customfieldvalue.

I have not seen an implementation of a multi-level cascading select list for Cloud. My guess is that it can't yet be done given the Cloud extension framework. I would expect one to have been written very quickly if it could!

You're right, I did not focus on the use-case. I concentrated at the utterly utterly broken "solution" and tried to explain why it was broken and a terrible way to do it. It's not only the wrong approach to archiving, it's also trying to use a technical process which is complex and breaks things. I have plenty of respect…

Email is a bad way to ask for help, and Atlassian take the much better option of having a set of Service Desks and issue trackers, which they guide you to the most appropriate one. Start at https://support.atlassian.com/contact Telephone support is hideously expensive compared with service desks, so only customers who are…

Yes, there are post-functions which can create issues at the parent level, not just sub-tasks of the current task. You'll need to use one of the apps in the marketplace to provide it though (or write one). Maybe have a look at the scripting or automation apps.

How else would you propose logging in without a login?

Monsters of Rock, 1986 - Def Leppard, Ozzy, Bad News, Motorhead

Licences are not "assigned to users". If a user account can log in (by being in a group set for log in), then they count towards your licence usage. Remove users you don't need any more from the login group, and add the new people to it.

Admin -> Issues -> Status allows you to add new ones, but to get them into a project, you'll need to edit the workflow for the project, adding the status in there.

Service Desk issues are only assigned to Service Desk Agents. Software users can be invited to participate, but can't be assigned issues, as they're not the people dealing with them.