Comments
-
What do you mean by "backlog view is missing"? Not there? Errors? If the board is showing as Kanban, then it is Kanban, not Scrum, and I suspect you're simply looking in the wrong place. Or, do you mean that since you created the Kanban, the project view is just linked to the Kanban board first? Can you select the Scrum…
-
Ok, you'll need to take a backup, and then run the process described in the documentation you referred to earlier.
-
You can give fields different "contexts" in the configuration setting for them in the custom field list. You can add several configurations by groups of projects or issue types (but there's a bit of a flaw in that you can't do both)
-
Not without rewriting chunks of JIRA's core code.
-
I think there's some stuff you can do if it is performed as an admin, but I can't remember. Even if I could, I'd point out that it's a security risk, and bad practice.
-
REST respects the rules you set for your humans. It wouldn't be much use if they could simply waltz around your rules by scripting a REST connection.
-
I tend to think of them as layers. JIRA Core provides you with a pile of things - users, issues, workflows, projects, searches etc. JIRA Service Desk allows you to flip a project from being a pile of "issues" over to a Service Desk, with a request interface in front of the issues. Agents then handle the calls coming in…
-
My guess is that you're trying to run this on a sub-task issue type already. Which will fail because a sub-task can't be a parent.
-
You'd swap to SAML. The Atlassian Account system for Cloud accounts does not yet support any form of two factor authentication, but if you use the other options, you can get some support. See…
-
Except that radio-boxes are simply select lists with a different front-end for the user. You need either an add-on to provide a select-list or radio-box field that tells JIRA it is a number rather than a string, or a way to translate it from select to number.
-
If you can see the transitions in the workflow diagram, but users do not get offered them when in the issue view, or trying to move cards around boards, then you have got Conditions on them that block the transitions, or your users do not have "transition issue" permission.
-
A nagging doubt - did you also install and licence Portfolio?
-
You can, and I've seen it done in a couple of ways. One was text fields on stories to capture the various fields, another was to have overall stories with the other data broken out into sub-tasks for individual authorisations/testing etc
-
In JIRA and Confluence all user based updates/transitions are halted, not just "create"
-
Why are you doing this? You can achieve the same far more cleanly and better with simple group memberships.
-
Ok, that might be useful information later. Your next step is to read the logs.
-
Click on the title above it. (System Default Field Configuration), then look to the right for actions.
-
I don't know, because I don't really know what you're doing. "Install new software" and "try to upgrade" are two totally different processes though (yes, same installer, but very different actions)
-
I don't know. Would a trial expiration disconnect your user management system? The logs might tell you what happened there.
-
That looks like a damaged installation to me, with missing supporting scripts.All I can suggest is1. Check the file(s) that it says are missing. If they are there, then do they belong to the right user and does that user have the right access to them?2. If they are missing, a re-installation is all I can suggest.
-
We can't tell you more than the docs do - where they leave off, it's things that are specific to your installation. To answer the bits you have said you're unsure on: 1. Depends on what you want from it and why you're proxying, but a proxy server can easily handle two installs on different ports and exposing them in…
-
No, you have to be able to log in. There are ways to reset a log in or swap to another known directory, but there's no point in trying them until you know what the problem is. You need to talk to your system admins (as in the server people), get them to read the logs to find out what the problem is.
-
If you can't create or edit pages, then that probably means you have an expired evaluation licence or you have gone over the number of users your licence allows for. Check the users and licence pages for info (there should be a highlighted box telling you if you're over)
-
It's a really bad move in my opinion, but yes, they are diverging them. Cloud users will be getting a new layout soon, which is totally different (around the overall framework, not so much on the contents like issue view, pages, reports etc, but where the main menus are etc). My third-hand understanding is that it's going…
-
Do you know what directory the JIRA is hooked up to? Are you certain it's the same as your "network" one? If so, then the next step is to go to the system admins for JIRA and ask them to look at why it's not reading/synchronising correctly with that directory.
-
You don't. JIRA Software does not support estimating sub-tasks. Even tricks that roll up the data on to a parent don't work because it double-reports it. The only trick I've seen that works is code that detects when a user puts an estimate on a sub-task, reads it off, adds it to the parent (or subtracts it, depending on…
-
And the errors in the other logs? The ones that *always* get written to?
-
You'll need to give us some basic information.
-
Sorry, I was totally unclear. The docs are correct, but the latest version is "Cloud" and that's different. Udemy has been documented on that, not Server. 7.4.1 still has the "more" menu. You're going to find more and more discrepancies, as Cloud and Server diverge.
-
You'd need a custom swimlane JQL for each issuetype, separately. The other options in the drop-down selection are coded into Software individually, there's no way to add any sneaky things into there without code.