Comments
-
I don't think this will happen with business boards. I suspect that if you ever end up in a place where you really need to do "board configuration", then you are in a place where you should be using "Jira Software". Atlassian are not likely to do anything that lets you do JS stuff in Core instead of upgrading to Software.
-
In terms of "why", it's mostly an edge-case. Most people who link in Confluence are either linking internally, or have no reason for "new tab/window", they've provided something for the user to read next. I am not saying it is not useful, I would use it. Just that it's not that important to Atlassian Confluence users, in…
-
JQL is for finding issues, not reporting on them. A JQL search or filter really just does give you a list of issues, and leaves it up to whatever is using the JQL to do the reporting. The reporting is done by what you chose to show your results with. The most obvious choice is the "issue navigator" which runs a search and…
-
Heh. You can actually see an area of desk larger than the bit directly in front of the keyboard, so I am impressed, and jealous. I usually have to swipe junk out of the way to put the laptop down. I've got an inch-thick stack of notes that I'm not quite ready to drop in the recycling, three remotes, some healthcare…
-
... and no "disable" functions. If you want to remove an issue type from a project, you have to convert the issues of that type to another (or move them out of the project). If you want to keep them, but stop people creating more, then, what Daniel said.
-
Excellent test. How are you doing the import and what are you telling it the date format is?
-
You have to provide import dates in the same format consistently. Pick one single format and make sure all your import data uses it.
-
You haven't said where you are starting from, so I don't know. But for Confluence, any version of 6 can go straight to 6.7. If it's 5.something, I'd recommend going to 5.13, then 6.0 then 6.7, but I'd actually try a 5.high (5.10+) straight to 6.7 - it can work fine.
-
Probably server. If you have only one server, then definitely server. For Jira, check if you are running Jira Core, Software and/or Service Desk. If you have Software, use that one (even if you also have Service Desk) Linux 64 bit will give you an installer, which is a better option for upgrades. Finally, check your…
-
The landing page when you first log into my.atlassian.com is the list of licences you might have. Is it not there?
-
The only way I can think of getting it to behave like this is if your "done" column is not the far-right-hand one on the board. Is that the case?
-
It's probably been added to your Jira by an admin to support the idea of "there is a group also responsible here as well as the assignee"
-
I don't blog often, but Adaptavist are asking me to do it more. See https://www.adaptavist.com/blog/profile/nic-brough I also plan to write Articles here when I get time
-
I'm sorry, this is the hard one to fix. Filters don't (yet) use ids properly, they are plain text, so I'm afraid you have to go fix every one of them manually. Normally, we're removing the target, so at least they give users an error when they need fixing.
-
What have you selected for your jira home directory?
-
No, apparently it remains vastly too expensive. They're also moving in the direction of encouraging chat and push notification over email.
-
You can't assign an issue to a group.
-
Thanks Julia! I also seem to remember this question was one we were not very happy with in peer review, because of exactly this "browse is not the same as create" quirk.
-
Identity Manager is the new Cloud user system.
-
?The view screen looks correct to me. I think what you're missing is that the view screen has fields deliberately grouped together by purpose and type of data. The way I usually try to explain how it relates to the "view" screen you define is that Jira takes the full list of fields you've put on it, and pulls out the…
-
Whilst you can restrict pages, an admin can always change the restrictions, as they can't do their job without that right. So, no. Keep your passwords in proper password safe software.
-
No. It was a Server product originally. Atlassian set up a Cloud provision arm for it a few years ago, so it's now both.
-
It shouldn't have, unless the post-function was not there when you copied the workflow. I would not worry about it, just concentrate on getting the workflow right for you. You need to do two things here: 1. Add the post-function for "set resolution done" on the transition into "done" 2. Add a post-function for "resolution…
-
I'm afraid Atlassian is inflicting it on everyone now, and removing the ability to revert back. We are mostly stuck with it now, and just have to hope they either fix all the things it has broken, or decide to go back to the better old interface.
-
Doesn't really matter which one you use, just pick one and use it for all projects in the board.
-
If you've looked through Atlassian documentation at all, you would have seen * A method to take the whole of Jira 1 to Jira 2 (destroying what was in Jira 2 already) * Project import (backup the whole of Jira 1, import issues from the backup into one pre-configured project) * CSV import * External import * Add-ons to do…
-
What do you get when you use the url with 8080 in it? The log should be under <jira home>/logs
-
By default, the Atlassian account is a System Administrator. If you do not use the System Admin group or that Atlassian user in your permissions, then no, they do not get to see anything other than the system settings. But, as system administrators, they can always give themselves access (although it's only Atlassian Cloud…
-
Yes you do. There is an "all" going into Done.
-
The "missing" types are removed automatically because their configuration is different to the two you do see. If you want to include them, make sure they share the field configuration and workflow with the two that are there.