Comments
-
Is this Server or Cloud? If it is server, then you are not in the system admin group - you'll need to check global permissions to see what groups are named and ask an admin to add you. If it's Cloud, then you are not a system admin, you're a Confluence admin. System admin is reserved for Atlassian support only, and you…
-
Depends on what you mean by "my account to start". Start to do what?
-
The validator is a red-herring, the error is happening later in the process as you try to post the data on the issue. Could we see the logs for the point of failure?
-
This sounds like you are using a function to copy status from a field into the status "field". Never do this. Status is NOT a field, it is an indicator of position in the workflow. You can't change status like this. You must use transitions to change status. There are add-ons that can help you with automated transitions.…
-
Sorting screens and status is pointless, so I'm curious as to what you think you would gain from it. Priorities have a sort order, you can drag and drop them, but the computer does not understand the words you are using for them, so there's no way to sort automatically. (Even if you could code for it, the schemes may…
-
I doubt it will ever happen - the area at the top right is for the estimation statistic, which can only ever be one value.
-
No, I'm afraid the field name always appears. I usually call it "note" or "guidance"
-
It is not part of Jira. Jira only ships with an obsolete user permission validator from Jira 2, and a proper permission validator. Check custom field is usually implemented by the Jira Suite Utilities (installed by default on Cloud)
-
Might need to explain "openshift"
-
How are you doing these check boxes?
-
But there's no way you can get the information you need in enough bulk to make that useful. If you've got to a point where you need to do this (which is entirely possible), then you've gone a long way down the road of "making data unusable". At a guess, I'd say there's a lot of people coming from a Remedy or ClearQuest…
-
Ok, I understand your view. But in the real world, the effort involved in writing a large amount of export code to create something a tiny fraction of admins might use isn't going to happen.
-
Could you give us a screen shot of the status properties? This has worked for me since Jira 2.3 to 7.7 so I'm sure we're missing something.
-
Yup. Upgrade it to 6.4, then 7.0, then 7.7.
-
Try jira.permission.work=denied on the step/status
-
Do NOT use the exe. This is a bundled installation of Jira Core and Jira Service Desk. It will create a new separate Jira with a Service Desk added. Instead, go into your existing Jira and go to Manage Applications. Add the Service Desk from there, and you'll get all the benefits from running in a single integrated place.
-
Go kick your local partner solution providers, many of them are happy to be invited and provide speakers to talk about their products, or more importantly, experiences. They often provide swag (and beer)
-
Nope, we're end users like yourself, with no more access to Atlassian systems than you. You should find the quotes and invoices are all available in the my.atlassian.com account you use for billing though.
-
Sounds like you've set something wrong then. Are you using odd characters in the username or password (anything not a-z or printed on a number key on your keyboard?). Check the log file to see what the error is.
-
Do what it says, ask your administrators. If you are the only admin, then see https://confluence.atlassian.com/doc/restore-passwords-to-recover-admin-user-rights-158390.html
-
A lot of gadgets run off filters, so yes, if you are using one of those, you can use a filter like "Project = A or Project = B" (Or more neatly "Project in (A, B)")
-
No. Again, Epic functionality works for Epics only. Then you have issues and sub-tasks.
-
The only thing I can think of is that we're looking at the config for a different board. Even if the project had multiple workflows and we're looking at one workflow that has it and another that does not, the group review status would appear in the review column in the config.
-
You don't create a board for a business project, they're always there. In Cloud. On Server, you can't, you have to use a Kanban or Scrum board.
-
I'm afraid not. The bar is very simple, it shows X transitions from the list of transitions that the current user can use.
-
In your view of the "Review column", you have "Review" and "Group Review". The next picture, of the board columns, is of the configuration of a different board, one that is for a project using a workflow that does not have a "group review" status in it.
-
No, the Epic functionality is built to work for Epics. To use non-Epics, you've already got the right idea - use issues and link to them.
-
Could you read the second line of the answer again?
-
For server, the domain must be a valid url. These use . as separators, and slashes are not valid at the domain level. For Cloud, your domain will be www.<something>.atlassian.net, where the <something> is a word you choose, without punctuation.
-
They both import everything, barring the config stuff named on those pages.