Comments
-
Scrum and Kanban are in Software, JSD provides the SLAs, portal and queue stuff. JIRA Core provides dashboards (alongside issues, workflow, fields etc), and if you have Software or SD, you get to use them too. I did think of a 2d filter as well, with Assignee down the left, but I'm not sure the groupings would be useful…
-
Ah, you don't have Software. OK, you can't really do this then. You're going to need an add-on or to add the Software application.
-
See https://confluence.atlassian.com/adminjiraserver071/migrating-from-jira-cloud-to-server-applications-802592270.html
-
Depends If it's Cloud, then no, because the server will be shut down and deleted shortly after you cancelled. If it's Server, then it's up to you - you can carry on running it for them if you want.
-
So nothing to do with "linked issues" Log in as an administrator, go to the project header and down into the "issue type screen schemes" to go find the "create" screen for the issue type. You'll be able to add the assignee and priority fields in there.
-
Sorry I missed out the second part of the answer originally!
-
What is a "Create linked issue Contractor and Priority"?
-
Confluence is a separate server, not an add-on or application for JIRA.
-
Start at https://confluence.atlassian.com/jirasoftwarecloud/what-is-a-board-764477964.html
-
Argh, I completely forgot. It was probably hidden by the field configuration as well!
-
There are two things that can happen with a field during a move. First, if the field is not valid for the new issue type, JIRA will warn you that you are about to remove it, and if you confirm, scrub it off the issue, writing that fact to the history. Second, if the field is valid, it won't touch it. But "valid" doesn't…
-
The closest I can get to that in JIRA is a board with swimlanes set to assignee.
-
The paste doesn't work, sorry.
-
Ah, ok, I misunderstood something. Your board columns determine what issues are shown on the board after the filter. So if your board columns do not include a status, they literally are "not on the board". So, first, make sure *all* status are mapped, and all your issues will be included on the board. However, there's…
-
Ok, I think you're looking in the right places, but the permissions are always complex to explain (there's a lot of flexibility in them, but that makes them not-obvious to administrate) I find it helps to think of them in two layers. First, you have "application access". This says "people can log in and use the functions…
-
It is the correct answer, but I did not explain it well. You need to set up the security scheme because that is the *only* way to hide issues in a project. You need to set it up with levels that enable you to select which groups can see what issues. You will need to set the right security level on issue create (and bulk…
-
Project administrators can not edit permissions, only add/remove users and groups in roles. As a full administrator, you can change permission schemes, but you should always use *roles* in permission schemes and stay well away from using groups in them. Certainly never put individual users in permissions.
-
JIRA 7.4 for that test, but I've also just tried it on 7.2, 6.4 and 5.2 to make sure my memory of the behaviour is correct.
-
On recent versions, try something like Project was X before date1 and after date2
-
People have shared filters with you. That's normal behaviour. This all appears to be down to filter ownership and sharing, rather than the upgrade. My other guess is that you upgraded from an older version of JIRA (i.e. 6 or earlier) rather than 7, as 7 changes the way users are handled, and that's had an impact on who is…
-
The only other off-the-shelf option is repeated bulk-edits to add the data to the new field before removing the old field. But I suspect you really want to use something like script runner to write a one-off script that will go through all the issues with a value in the unwanted field in one go, updating the other.
-
I am guessing you mean in JIRA. The answer in there is "run filters for the issues and read them, then think about using them in gadgets on dashboards in order to get more helpful views of the data"
-
Ok, the only possibilities now are a massive bug no one else has reported, or your project is not using the "plugs" issue type you think it is. To help with debugging the first one, try re-indexing the project.
-
You must be missing something in the configuration. I've just created a new radio button field with three options, and made it mandatory in the field configuration (for all issue types in the project). None is no longer an option when creating a new issue. One other thought though - could someone have added "none" as an…
-
Can you tell us what roles and groups Alina is in? And exactly what the "assignable user" rule is in the permission scheme?
-
No no no. Cancel that, you're doing totally the wrong thing. PLEASE, read the answer I gave already. All of it. Properly.
-
It was probably not the upgrade directly. What I think is most likely to have happened is you have a field provided by an add-on. The add-on is not compatible with 7.4, so the field is no longer working. The filter your gadget is using references that field. Hence you now have an invalid filter, which cascades back into…
-
Again: Set up a new project on the target system, configure it the way you need it. There are addo-ons that can help you copy the configuration over
-
What type of directory does Tivoli expose? Last time I used it, it was a proprietary one that didn't really work with anything properly, so it wasn't supported, but that was a very long time ago.
-
Please read the first answer properly for the first two. You will need to install service desk on the target as it is a new install.