Nic Brough -Adaptavist- Expert

Same here, it's hidden empty fields since at least 3.0. You'd need to hack some core code to do it as well, it's not as simple as an app or injected code to override it.

You can't apply properties to custom fields. Also, permissions apply at a project level, to issues, not to fields.

I know what you mean. JQL queries are one of the things I often need someone else to check!

You've defined a query that can not possibly return anything. Just looking at the bit that causes the problem, and shortening it a bit), have a think through what this really says: assignee not in (A, B, C, D) and assignee is empty There's two possibilities there, the assignee is either filled with something, or it is…

No, because you've asked to do something that cannot work. I can't do the impossible.

I'm afraid repeating a statement that has been questioned does not help. Could you tell us what you are trying to "access" in Core?

What part of core can you not access? What are you trying to do that is blocked and how is it blocked?

By "Request type", do you mean you have an issue type called "Request" (or "Request type") or do you mean you are looking for the Service Desk Project settings for Request types? If it's the issue type, then what @Joe Pitt said. If it's the service desk requests, then check that the project is a Service Desk project, not…

The "missing" tabs contain only fields that you have not put data into. Jira hides empty fields, and if a tab has nothing but empty fields, it will hide the tab too.

There's been no change since the discussions you've seen.

For someone to have access to Jira they need an account. That account is provided by a directory of users. So, to use an Outlook list for access, that list must be translated into accounts in the directory of users, and possibly a group which you can then use for access control.

Repeating the statement with slightly different wording does not * explain what you are trying to do. Is it data feeding into and/or out of Confluence, or or you trying to use MongoDB for the Confluence database? * explain why you are posting the statement here. What do you want from us?

Look at the screen scheme for the project (assuming it's a Classic project), that determines the create screen for the issue (not the request)

Have a run through https://confluence.atlassian.com/confkb/confluence-upgrade-failed-with-liquibase-exception-lockexception-could-not-acquire-change-log-lock-error-969527207.html

I suspect you have a custom field called "workstreams" which has been flagged as "mandatory" in the field configuration for the project.

Ok, can you explain what this has to do with Confluence in more detail? And maybe give us a question, rather than a statement? There are two things I think you might mean here: You want to connect your Confluence to your primary data source to get some data out for display in Confluence (or possibly even read it). You'll…

For 56 users, you will need to be on the 100 user tier.

No, Cloud does not support this.

The change will be recorded in the issue history, you'd need to copy and paste it back out of there.

You will need to get your DNS set up to resolve the desired url to your server. Then, make Jira run on that server, or at least, appear to. You can do it with plain Jira (although it will then be your whole domain), as it's running on a Tomcat you expose as a domain. However, most of us will use a proxy so that we can…

Nope, we cannot tell you - we're end-users of Atlassian stuff (of course, there are some Atlassians here), and we have less access to, or knowledge of, your servers than you do. If you can still log into it though, have a look in the admin -> applications or admin -> system info.

First, I would talk to your users, they need to understand that "hammering on reload button" is what is making it slow and they need to learn to stop doing it. There are a couple of things to look at. I would be considering moving to data centre if you have severe loading issues. There are two things you could do with DC…

This suggests you have some form of automation or script which is changing (defaulting?) the descriiption field during the move. You'll need to find and remove that.

So, your iTrack is a Jira installation, so we can offer some guidance, but we're not your admins and we do not know how it is configured (especially as to what you might be using to create "scrum teams"), so it can only be generalised. You will need to talk to your administrators about creating scrum teams.

You can also request Atlassian support to change it. They will not do this regularly or frequently, so choose a good url if you do make the request as they won't change it again for a whle (For some reason, I've got a year lurking in my mind, but I would not rely on my memory)

You will need to read the application log to find out why it is locking Jira. You should find the important one with the reason in it at <jira home>/log/atlassian-jira.log

If you want full accuracy, you would need to install geo-tracking software on their 'phones, and in most countries, obtain explicit written consent to track people. If you're content with attempts at geo-tracking on the server side, you'll need to find a power-up that can hook into a geo-location service and try to report…

This is what it says it is, the Confluence server cannot reach the database server over your network. Are the settings correct? Can you try going on to the Confluence server and running a simple telnet to the database host and see if it responds? The error message you will get will probably tell you where the fault is.

I think this is close to what you need : https://library.adaptavist.com/entity/calculate-custom-field-on-issue-update You'll need to modify it to read the links and work out what issue to update instead of the current one, but there's some code for working with links in…

No, it's not changed.