Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! This would suggest you are not a Jira admin - you need to be an admin to create or edit permission schemes.

Welcome to the Atlassian Community! This usually happens when you try to use the same key with two different accounts. You should not generally be sharing keys between accounts. You can fix this by generating a new key for the new account.

.getParentObject() will return null if the current issue is not a sub-task, but it mght also be that it can't render the object directly as plain text in your error message. Try issue.getParentObject().getKey() for the issue key in plain text.

@Craig Nodwell is right - a disabled option cannot be selected when creating or editing an issue, but remains on existing issues it was applied to, so you can still report on it. Deleting an option strips it from all the issues it might be on.

Jira only deletes issues if told to by a human (whether it's done via the UI, REST API or by an app that your admins have installed). I'm afraid all we can tell you is that one of your people did it.

Welcome to the Atlassian Community! We can't tell you - you have not explained what a Service is to you in your Jira. It would be better for you to not read the database though, the REST API will give you much more detail than complex and inefficient SQL.

Welcome to the Atlassian Community! This is something you need to ask of the owners/administrators of your Jira system. We can't tell you how your organisation wants you to use their Jira.

Welcome to the Atlassian Community! I think you need to ask your Jira administrators for help with this, we, the community, have no sight of your system, let alone the administration of it!

Welcome to the Atlassian Community! You should never be updating status based on a custom field. Status changes because the issue moves through the workflow, which is something your humans or automations should be doing at the right time. And you should never have more than one status field, the status is an indicator of…

You'll need to find or write something that can reach into Sharepoint and extract the data. I'm afraid we can't really tell you a lot more than that, you just need to find or write something to add to Jira that can go read your Sharepoint stuff.

Be aware that fields are locked to stop you from messing up their configuration and breaking your Jira. It's almost certain that your desire to unlock them is rooted in a request to do something to your Jira configuration that will break it. Before you unlock anything, could you explain why you think you want to?

If you need a second opinion on this one, then I'll chime @Joseph Chung Yin is exactly right. You have not been able to change user numbers since February this year, as Atlassian announced a few years back, and it is illegal for you to use someone else's licences. The only way to increase your user numbers is to migrate to…

Welcome to the Atlassian Community! It sounds like you've moved from a legacy system that works in a very silo'd way over to Jira. I'm glad to say that Jira doesn't inflict poor naming conventions like that on you. The issue key is unique and tells you nothing more than the project the issue is in. You can implement your…

Welcome to the Atlassian Community! Start by training your SMs to use the "create linked issue" function in the service desk. This lets them copy the issue behind a request into a development project. Once they're doing that, you can set up Automations that can watch for change on the linked development issue, and push…

That's a poor user experience - people don't want to have to scroll down a page to enter more information. Because it's not a great way to present the request to people who want to comment, Atlassian don't enable it.

I'm not entirely sure how you're creating Palm Beach Airports in Jira, but I'll assume that your TLA means something else. The "team" field is not automatically set by Jira by default. What have you set up to do the automatic assignment? Is it just the field defaults, or something else?

There's no bulk export like this. Mainly because it's not needed. Why does your manager want a pile of pdfs they're never going to read? (If they do intend to read them, why don't they just look at Confluence? It's easier to read than a static pdf, and not obsolete as soon as you look at it)

Welcome to the Atlassian Community! Yes, but the work you'll need to do on it is about translating the data from whatever Odoo can export into a shape that Jira can import. What export options does Odoo have?

Welcome to the Atlassian Community! I can happily recommend the first four of apps on https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=survey plus the Upraise one for something a little more focussed than a generic "survey"

Yes, it has to, because you're running it in a different place.

Welcome to the Atlassian Community! Generally, you should not be creating issues straight into an active sprint (or even a future one). As work arrives, it should go into the backlog, get refined, and then be compared with the rest of the backlog when the team are selecting what needs to go into the next sprint. Is that…

Welcome to the Atlassian Community! This is down to the "working hours" that Jira looks at in the time-tracking functions. The sprint gadget is "prettifying" the number into your settings for working days. Go to Admin -> Issues -> time tracking and check what you've got set for the working day. I suspect you've got the…

Welcome to the Atlassian Community! I'm afraid most of the gadgets Atlassian plug in to a standard Jira install are pretty much hard-coded. If you don't have an option in the "configure" screen for a gadget, then whatever the setting is, it is hard-coded and you can't change it.

Build it into the workflow for the customer - literally, let them have an "escalate" option on the request so they can yell for help when things are stuck. The issue behind the request will probably need to have its workflow modified if you do escalation like most people do. Most add an "escalated" status to the flow, and…

You can't see the filter for some types of board, but on those, we know the filter is hard-coded to "all the issues in the project the board is for"

FWIW, the cog icon gets hidden if you don't have any admin permissions anywhere. It appears if your account has any one of the permissions John lists - site, Jira admin or even just project admin for a single project.

Welcome to the Atlassian Community! There are a number of things we need to look at to help with this one, so to get started, can you tell us what you get when you go to "configure board" - the ... (or the configure option in the menu it pops) towards the top right of the board display. Does that give you a load of options…

Annoyingly, you can't remove locked fields, and the removal of the JSM app doesn't do it either. You'll need to get Atlassian to remove them. All you can do as an admin is flag them "hidden" in all your field configurations.

Welcome to the Atlassian Community! Confluence is indeed a wiki service, and if you're starting from scratch (or moving from other systems), I would recommend you think about two things here: 1. Structure. Confluence divides its data into spaces, and the configuration is generally hung off the space. So which users can do…

Welcome to the Atlassian Community! Admin access to Jira could be of many different things, but there's no single flag you could put on a profile to identity it. Whomever gave you admin rights may have given you * Project admin in a project (this is done by the permission scheme in each project) * Site admin lets you…