Nic Brough -Adaptavist- Expert

It's evolved into an "application access" group. Check Admin -> Manage Apps to see what group(s) are the "can log in" groups for each application. The "solution" remains the same - you have to give the person an active account, with "assignable user" permission in the project, in order to assign issues to them

So, you do have the resolution field on-screen. I wouldn't worry about the "pops on screen", it will go away when you remove the resolution from the create screen - you need rid of it.

If you would be ok with a 90 degree turn, just use seven filter statistic gadgets (yes, you'll need a 7th saved filter that includes all the definitions of the other six). A filter statistics gadget's important parameters are "filter to summarise" and "field to group by". You can see where I'm going with the first, the…

What is the query behind the gadget and what are the two axis selection fields? (Feel free to obscure actual selection data, we're only interested in the clauses in use and how they're joined)

Depending on where you're seeing this, it is mostly configurable (project type; team or company managed, and which issue view option you're using determine what is configurable here and how you get to it!) The fact you've got "source" in there is a giveaway that it's configurable though - it's not a system field like the…

Jira Cloud systems now autoscale to cope with load in general, but you can still have performance problems if you're doing things that do not respond to simple scaling. Start with a look at what is slow. Everything? Boards? A particular project or set of them? Certain users or groups of users? REST APIs? Dashboards? How…

<field> is empty Will list all issues where a field is valid for an issue, but has currently not got a value.

Yep, one of your administrators has added a link type for "treats". You'll need to ask them what it is intended for.

https://library.adaptavist.com/search?term=jql gives you a swathe of scripts that use JQL to do things.

There's nothing specific for a list of fields, but you can save yourself 99.9% of the "picking through the documentation" by hitting https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-939938733.html scrolling down a way until you find the table "Reference" and expanding the line "show list of fields" in…

You don't, that is not what templates are for. A template is a shape you use when you initially create a new object. The object takes on the shape of the template and then you use it as is, or change it to suit things. Changing a template can't have any effect on the objects created using it retrospectively. They're not…

So the github side is in error. That tells us that the connection parameters you are giving github are wrong so it can't connect (or possibly that your network is not allowing the connection, but as I can see your Jira on the internet, I think that's unlikely)

The issueLinkType clause looks at the type of link, it does not consider the issue on the other end of the link. Is that what you think is wrong with your results? It's not looking at the other end of the link?

"retrieve" is a synonym for "get" in that context. It does not explain what you mean by "get" The reason I'm asking you to explain "get" is that there is an obvious answer: You can "get" a list of projects by going to the list of projects in the UI and reading it. I don't think that's what you mean. It's the correct answer…

Worklogs are not stored in customfield, and nor is much of the sprint data. I would very strongly recommend that you stop reading the database, it's the worst way of asking Jira for any form of report - it's not designed for it, your SQL rapidly becomes a nightmare, and unless you have a comprehensive understanding of the…

My guess is that you have "public links" enabled. This is incompatible with anonymous access and when enabled, removes the anonymous access tab from permissions. See https://confluence.atlassian.com/ge/public-links-979425312.html

That is something that's a little confusing, as it is counter-intuitive. It would not be unreasonable to have coded some checks into it - It is possible to code for "check this user/group you're adding for edit can actually see the page given the current restrictions". At the moment, Confluence simply lets you add anyone…

Could you explain this more? What you you mean by "rework custom fields into classes" and "relocating"? Yes, you can have as many custom fields as you want (could you explain "classification" though?), but that doesn't help with getting a custom field of a certain format as was asked for.

What do you mean by subdomains here? Product subdomain and organisation subdomain don't mean a lot when you have not described the context in which you are using the phrases.

Thanks Vikrant, I should have said that, but I think my brain shut off when it saw the "server" tag and decided not to type any more!

Ok, there's a couple of problems here: def intMonth = issue.getCustomFieldValue(cfIntervall) as Integer; return intMonth; This will exit the script, returning simply that month number. It's never reading the second custom field, let alone doing anything with it. def…

User macros and server apps do not work on Cloud. You will need to evaluate what you have done with them all and see how to translate them to Cloud. There are similar functions, and you can create things for Cloud that can do some of the stuff you've done on Server, but you are looking at re-writing them mostly from…

Your admins can set up links with whatever names you want, so I'd ask them what they intend you to use "treats" for (I'd bet on what Mikael said though!)

You'll need to read a lot more tables than those. Comments, issue history, (multi-)user pickers, and and and. A far more simple solution - go to the list of users and deactivate any user who has not logged in within a reasonable length of time. That way you won't lose data or have to migrate it all when you drop them…

Then no, because the issue key is always <project>-<number>

Summary is the only user-enterable field that cannot be left off an issue. An issue also belongs to a project, is of a type and must be somewhere in a workflow (have a status), so although they're not really fields, I suspect they should be on your list. There are some derived fields you can't get rid of - created,…

The identifier for an issue is <project key>-<sequence in project> Epics don't care what project their stories are in, so yes, you can do exactly what you describe by having your Epics in project ABC and the issues(stories) in XYZ

There's no explicit way to do this, but you can do it indirectly. Create a second transition that mimics the existing one, has no validators, but has a condition on it like "can only be done by <user x>", then run the automation as user X and use the new non-validated transition. Oops, sorry, I forgot - you can also tell…

To be clear, the core/business boards are not Kanban boards, they're just boards. Things should drop out of the done column after 14 days of no updates on them (this number is not yet configurable, but as John says, it's on the list) On a Kanban board (Jira Software), you can configure the filter that drops things off the…

I'm very confused. You say you've restored a backup, and you say you're using postgres, but your system information says you're on h2, not postgres. So what did you actually restore? A postgres backed Jira or an h2 one? And did your backup process include the attachments? If so, then how?