Nic Brough -Adaptavist- Expert

You need to stop doing this, you've misunderstood what the resolution field is for. The resolution field has two broad states - * Empty - the issue is unresolved and needs more attention * Filled (with any value at all) - the issue is resolved and will be seen as complete by most of the reporting in Jira (including putting…

Welcome to the Atlassian Community! The snapshots are mostly there for reversing a failed indexing run by hand (rather than fixing what caused it to fail and then re-running), so it's going to be very unlikely you need more than the last one. (Keep two or three if you're feeling paranoid)

Best way to do this would be a simple post-function on the "close issue" transition that looks at your custom field, and sets the resolution accordingly, without asking the humans.

I am really sorry, I've told you some total junk there! Well, the idea is right, but I've picked the wrong method. Longs are integers, they can't handle decimals. So, I'm sorry to have to make you re-do a load of edits, but try: def calc = ( Double.parseDouble(BPS) / 100)

Ok, so you'll need to code Exact Globe to send REST calls to Jira to update its issues, and maybe think about coding Jira to send calls to Exact Globe if changes happen on the Jira side that EG needs to know about.

Ok, for filling it, see the second paragraph of my comment. Sprints are different to the rest of Jira, they look at the board, not the resolution. I am going to guess that your "Done" status is not in the last column on the board, so the sprints can't see it as "done".

The urls you are using in there are the same, so there is no "different platform", or "different in different countries". You're all working on the same service. Look at the line below the name of each project - one says "Business project" and the other "Software project". These two project types are intended for very…

Are you going through a "resolve issue" screen when you close the issue?

Welcome to the Atlassian Community! I'd strongly recommend getting one of the Power BI connector apps from the marketplace. These avoid you having to read and understand the database (it's terrible for reporting and trying to do it yourself is a LOT of work)

I'm sorry, but that does not help explain what you are trying to do. To me, it sounds like you are creating three custom fields, let's call them cf-1, cf-2 and cf-3, all with the same possible options (let's say, the options are alpha, beta, gamma, and delta) What you said you want to do is when someone fills in a new…

Welcome to the Atlassian Community! For Data Center, all the data lives in the database, apart from attachments, which live on the shared storage. The installation and working data also lives on each of the nodes in the cluster, alongside the shared storage.

No, this won't be disabled, because you need to create and maintain schemes for Company-managed projects.

Welcome to the Atlassian Community! Could you explain what this has to do with Confluence?

Welcome to the Atlassian Community! I've seen a couple of posts similar to this before. I'm afraid you have clicked on "help with Confluence", which lands here, rather than "help with the data" which should go to the organisation you're working with. My guess is that you're looking at data from ECMWF, as that's where I've…

Resolution is a system field that asks people for a broad reason that an issue was closed (fixed, done, duplicate, cancelled, etc) and also acts to tell Jira whether an issue is "resolved" - if it is empty, most of Jira considers the issue "open" or "unresolved", if it has a value set, the issue is "resolved" and needs no…

Welcome to the Atlassian Community! You'd need to ask the people who set up that Jira to ask you for that data. We're a community of people who use or want to talk about Atlassian stuff, but we can't know how everyone's Jira is set up or why it's asking for certain pieces of data. Have you tried asking the people who asked…

Yes, Jira has a REST API you can talk to from other systems, and webhooks and triggers that can be set up to talk to other systems. So, yes, it can be "integrated" with other systems. The next question is "what do you want from an integration"? 

With some scripting or automation, you can do this, but I want to question why (I don't think I have actually understood what you are looking for). Why do you want to put the same value on an issue in three different fields? Surely you only need one field?

Have you set up and applied a different workflow scheme?

The workflow for an issue is configurable by issue type - if you open up a "workflow scheme", you'll see it lists which issue types use which workflows in the project you apply the scheme to. So, no, Epics in a project can't have different workflows, but yes, you can have Epics, Stories, Bugs, Tasks etc all use different…

Welcome to the Atlassian Community! What do you mean by "courses"? Are you representing something you call a "course" as issues?

I prefer to say Cloud has Team-managed projects, and Server DC only has company-managed (and no need to name them as such because there's only the one choice available)

Ok, so you have numbers in text fields, the trick there is that you'll need to read them out as numbers (you can't just wedge strings into number fields, they need to be interpreted) From memory, the easiest thing to do is use the parse functions in Java - assuming BPS is a string that contains a written number, try def…

How are you expecting Jira to know which issue to comment on from an email that does not have any information on it about which issue to look at? There's nothing that can be "fixed" here, you need to give the issue key to the users so they can use it in the subject of their emails.

Start by working with Forge - see https://developer.atlassian.com/cloud/jira/platform/forge/ for getting started with that.

Yes, go to site admin and choose a new name. It will still have to be a .atlassian.net address, as Atlassian still don't have a way to run Cloud on other urls, but you can change the name yourself now. I don't understand what you mean by "and not in paid subscription" though.

Copying JQL is not going to help you. You need to create a new query that selects everything you want to see on the new board. Look more closely at the two queries, they look to me that they are directly conflicting (component = NIC and component != NIC is going to exclude every issue that has a component set). You need to…

Probably. What are you using to run scripts?

What a horrid thing to have to do! Why don't you do the reporting properly by writing a simple REST call to get what people say they need?

Welcome to the Atlassian Community! You need to decide if you want a field that can accept new values from the user or not. Label are ideal for what you describe for the end-user, but you then say that you want to limit what they can put into the field. Which is it?