Nic Brough -Adaptavist- Expert

Because -1d means "1 day ago", not "yesterday" Try > startofday(-1)

Welcome to the community! A crowd administrator (not a user with rights to maintain the users in crowd, but the Crowd system admins) can always log in. They have to be able to get in to be able to apply a new licence. They will be able to reduce your user count as well, even when you are over the limit.

There's no reporting on the configuration of Jira built in, it assumes that admins can look at the admin screens to understand what it is doing (and that's not actually wrong - taking the admin data out of context reduces its usefulness for anything other than analytics) There are apps you can add which can generate…

Welcome to the Atlassian Community! No, labels are just a simple word or phrase you write on a card, there's no metadata for them.

There are three things this could be: * The issue does not exist * Your account does not have the "browse" permission in the project, so it can't see the issue * The issue has a security level set and your account is not in the security level the issue is in Your admin rights don't have anything to do with this, they just…

Hi Reagan, Jira's hierarchy is a bit rigid, even since the DC/premium stuff started to give us a bit more flexibility on renaming things. This does get a bit messy because of the history, which I won't bore you with. * Plain core Jira has Issue -> Sub-task * Jira Software gives us Epic -> Issue -> Sub-task * Advanced…

We can't do it for ourselves, but I think Atlassian's Khoros developers can do it. I'm not sure who your community manager might be, but they are the person to ask first. If you're not sure, then let us know and we'll throw the question at all of them ;-)

I'm afraid they've been told that many times before. Including by me (as an Atlassian end-user, not an Adaptavist). I would like to point out that DC is not just seeing bug fixes, it is getting new features, but they're not as rapid or as experimental as the ones for Cloud. Recently, we recommended that a client doing an…

The only way to remove the options there are to remove them from the issue type scheme, so they can't be used at all.

Forget the field configuration, it is not the problem here. The code for Epic link looks at the issue type and the field itself, but it is not mandatory anywhere (you can't put it on Epics or sub-task types). I suspect your error is being driven by something else. Could you give us the exact text of the error?

I suspect you may be looking at a team-managed project in Cloud Jira. These have only one sub-task, you can only enable one type and it's called "sub task". For a company managed project (Cloud, Server or DC), Daniel's answer is the one to mark correct.

What do you mean by "private cloud"? Do you mean a (secured) Atlassian Cloud system, or Atlassian software you are running yourself?

Ok, you absolutely do not want to do file transfers with Jira. It's not good with large files. What you really mean is that you want to take attachments from one Jira server to another. Jira attachments are done as simple uncompressed files living on the file system, and you can use any server-to-server transfer system…

You don't. Bitbucket is not a web server or a web application server, it is a source control application. None of it is written in php, so there's no need for it Could you explain maybe why you think you want to add php support?

I'm sorry, I'm still stuck, could you tell us what a poststep is?

I think that's one that Confluence can't read. Sorry.

Are you using the Atlassian account to log in (the one you are using to post here in the community), or trying an old Trello account?

Do you want to remove the issue type field from the screen, or actually remove the issue types from the project?

Ok, the fact the space moves through the middle of the words on resizing tells us that there is something wrong with your browser. It is possible to cause CSS to do this, but neither the old nor new views do it. (Open the page where it is happening, and select "view source" - it's a wall of text, but it does not contain…

I'm afraid not, the boards default example quickfilters are coded in. For Company managed projects, Atlassian got such a wide range of suggestions for defaults, there were only a couple that jumped out as being good defaults. For team-managed projects, the main aim is getting the team going without asking them to configure…

What does "it does not let me log in" look like? you give it your email address, it asks for a password and then what happens? What are the error messages? Как выглядит "не даёт войти"? вы даете ему свой адрес электронной почты, он запрашивает пароль, а потом что происходит? Какие сообщения об ошибках?

Take a look at the configuration of your incoming email process - is it a JSM email channel, or a Jira email "handler"? Both read the sender, but do slightly different things with them, and that is configurable. The standard email handler for example, tries to import the sender as the reporter of the issue, if configured…

I am not sure you can, but you should talk to Atlassian about it. Go to https://support.atlassian.com/contact and select "Billing payments and pricing" from the list

What template is the scripted field set to have for the output? Confluence can only read some of them.

From memory, .reqif files are xml based files for exchanging requirement documentats. Confluence is not a requirements management tool (although some do use it for requirements), so there's nowhere to import most of the data to. You could attach the raw files, but if that's not good enough, you'll need to find or write…

There is one small catch in what Alex has said. When you are checking the permission scheme, you need to be aware that JSM projects handle users differently and the permissions for a Software or Work Management projects are usually not suitable for JSM projects. You can end up with Jira complaining that there are errors in…

The official page you probably want is at https://confluence.atlassian.com/enterprise/managing-custom-fields-in-jira-effectively-945523781.html Bear in mind the article is based on testing Jira 7, rather than 8, so the numbers are not particularly useful to you. As I said, Jira 8 is a lot less affected by the field…

Admins permission is for admin functions, not project rights. They do not grant "can do anything". Check if you have create issue - click create and saa if you can select the target project.

My guess is either what Tom said about dropdowns, and about permissions as well - to move an issue into a project though, it's not just browsing, you need "create issue" permission in the target project as well.

Glad to be of help! For tabs, go find the screen you want to break up into tabs, and go in to edit it. You'll immediately see that there is a list of fields there, but look just above the first one - a default untabbed screen will have "Field tab" with a pencil mark for renaming it (you don't need to when there is only one…