Nic Brough -Adaptavist- Expert

Go to project admin, find the "issue type screen scheme" and drill down into it to find the edit screen for the issue type(s) you want to edit, and that will take you to the screen definition. Remember to remove it after the bulk edit to avoid your data being utterly mangled by users doing nothing wrong.

No, I don't know how your data works or how you want to detect when the data should or should not be updated - that logic is up to you.

You will need to revise all the permissions, removing access from groups and users for the projects they should not see.

You will need to go over all your permissions, removing access from people who should not see a project.

The "return" directive ends processing of the script as it feeds back a result.

Nothing to do with Software. One of your admins renamed Open to To Do. There's no other way this could have happened. You've done exactly the right thing in changing it back, it's not a "work around", it's the right answer. Next you'll want to find and educate the admin who made the change.

Sorry, but the same question applies. Add what? (Actually, I know exactly what you're looking for here, but the answer of "it does not make sense" remains the correct answer) That's a very tech-based responese. I would like to step away from the tech and simply ask "what is the question"? What are you trying to answer or…

Nothing wrong with ranking issues as they matter to you. The question on how you do that organistion is about how you want to do it, and hence how you want to map it on to the way Jira does it

Atlassian tend to support ranking your issue so that you can be agile

Ah, sorry, I had the page open and didn't see that you had found it before I answered.

Log in as an admin, go to any admin function, click search, start typing "timetracking", the autocomplete will do it.

Go to Admin -> Timetracking, you can edit the number of days per week and hours per day in there. There's couple of other things there I don't think I've ever touched - my clients through my career all seem to want a 40 or 37.5 hour week, with some minor exceptions (charities with volunteers) wanting 1 or 2 day weeks, and…

Jira does not have a framework for "apps by project" - apps are installed at a system level and become globally available. That is just the Jira framework though. There are a lot of apps that provide per-project configuration, some even need to be actively enabled by an admin in each project, although most make themselves…

Is the second scripted field on the same issue as the first one? This will often break because you can't be sure which field will be recalculated first when the issue is reindexed (or, in fact, how many times!). The way to "fix" that is to not base a scripted field on another one if they're going to be indexed in the same…

Where are you storing these dates?

How are you storing the start and end dates on the issues?

I can't help you I'm afraid. You'll need a valid jar file (the name of this downloaded one suggests it's not really a .jar file for a start), and use that.

CFDs represent either the board, and you can change the date range with the drop-down at the top.

Start at https://confluence.atlassian.com/jirasoftwareserver081/getting-started-with-jira-software-970610697.html

Yes, you need to give it a number, not a string of custom field names.

The REST API does not support that. You should use the meta-data fetch if you want to know what is available.

Which ones, and what are you expecting from them?

Could you please tell us what the base url is set to?

I'm not doing anything differently to you. Hitting the rest endpoint with a curl backed json payload.

Ok, so you don't have export rights. Check the space permissions.

You'll need to add some "if" code to the top of the script - somehow do "if already added this one up, exit without adding it again"

That is very odd, it works for me. I think, yes, you may need to report it as a bug.

And the base url is set to?

Are you saying decimal values are not working?

You don't want the screens, they only contain 1/3rd of the config that could affect how an issue handles its fields. Grab the field metadata instead - this will give you the full list of things you can set on an issue. See…