Comments
-
Enable the special "current reporter only browse", use it for "browse" permission, and lock out all the other "browse" permissions. (E.g. Allow "browse" for "current reporter only" and "internal developers" only) See http://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission
-
That's a fair comment - some docs do it ok (A lot of Atlassian stuff has a version drop-down near the top) but some don't even try to hint at a version. I guess you ran into one of the latter! I wasn't sure whether you needed applications, as I don't know what doc you'd found, but the search was a start.
-
Applications only went into that menu in JIRA 7, and it's referring to Core, Service Desk and Software. For 6.4, hit any of those options you have in the image, and you'll be in the admin interface. Frankly, I have no idea where most things move to in here across all the versions (I started with JIRA 2, things have moved a…
-
I'm assuming you have got the default setup, which puts jira-users into all projects and hence says "anyone who can log in is in every project as a user". To fix that, * Add the users into the roles in the projects they need to see. * Remove "JIRA users" from the roles that grant it access to all projects. * Consider going…
-
Answers seems to encourage that, I just respond to prompt people to do exactly what you've just done! The JIRA view screen rearranges a number of fields, gathering together the people, date and "system" fields (including description) into distinct sections, which is why it's ending up in a funny place. I'm afraid this is…
-
Yes, you can have them in JIRA.
-
I have to agree with Christian here. Some teams don't need "reopened", "open" is good enough. Other teams really do need it. The classic case is support type stuff - the team resolves it, you reopen it because you don't think it's fixed. If you simply go back to "open", you have no idea that the team has had something old…
-
Start with a handful of Service Desk Agents. Set up the service desk so it includes things you can break down into two broad categories - service, and development. When an issue is a development one, you need a process to triage it - some of them will lead to development requests that should be duplicated over and linked,…
-
Actually no, it just requires that your agent has access to the project. Agents have "core" access so they can be given access to development project issues like this. Without a software licence, they won't get the boards stuff, but they can still be users in the project and use the issues therein.
-
It adds the linked issue to the backlog on my system, so I'd say the video is correct. My best guess is that you've not configured your board to pick up the issues you are creating.
-
Definitely. And to help with the "don't want to use a transition", you can do it as a listener instead.
-
Service Desk is the best answer. If you don't want that, then two options: * Create a custom field with a date/time, and use a post-function from an add-on (JSU) to put the current date/time in it on the transition you are interested in. * Use Script Runner to create a scripted field that exposes the date from the history
-
You can restrict who can "browse users" in Admin -> Global Permissions, but it is all-or-nothing, a user can either see all the other users, or they can see no-one.
-
Hmm, that really does make a lot of sense, I hadn't really grasped that before.An idea on improving the idea of a simple flag - instead of a really plain checkbox, use a custom field of some sort. There's a few options here - a multi-select naming the "interested teams" would be a much better option than a simple…
-
I can't see how a custom field with a list of boards would be any better than a simple flag field on the issue saying "interdisciplinary". It's actually worse, because the list of boards is going to change and adding a new board is going to require you to go back over the field and get the humans to update it (not to…
-
You'll need to write some code for that. I'm not sure you'd want to do it as a checkbox too - JIRA Agile users often generate a large number of boards quite quickly, and it's not unknown to find a JIRA with hundreds of them, which doesn't really translate cleanly into a neat checkbox. I think it might be easier for you to…
-
"Whenever you find a bug" is the basic answer. Exactly how you handle it is up to your processes. Some places simply accept new bugs as they're found, with them all going into the backlog. Some places differentiate between a "bug" and a "defect" by saying that bugs are found in production, and defects in testing, and then…
-
Ok, this definitely needs to go to Atlassian support.The query "project = Key and fixVersion is empty" should be returning these issues (assuming there was only one fixVersion, and that's the one you deleted). The next step would be to read the logs, but you can't on Cloud. It's definitely broken, and they need to take a…
-
You're right, you really should not have to do this. It should be empty
-
Right, so you are on Cloud. When you deleted the version, which option did you choose? "Remove version" or "swap to other version"?
-
Ok, that sounds like a bug - when I delete a version on the demo system I have here, it is removed from all the affects/fix version fields in my projectCould you try re-indexing the project (in the project admin screen) and check the Kanban board again?
-
I apologise, I was not clear there. When you "removed" it, what do you mean? Merge? Release? Archive? Delete?
-
If you delete a version, it should be stripped off the issues as well. How did you do the "remove" of the version?
-
Renew it with the SSL certificate provider, and then install it on the server as you did with the previous one.
-
Ugh. Someone has done it, it's certainly not in the core distribution, you have to work at it. Some ideas to check: * Last time I was messing with GA, it was possible to get a simple set going by adding a call into Admin -> Announcement banner. Look there first, as it's a quick one to rule out. The banner appears on every…
-
Er, yes, I understand the need to turn it off, but it's your system, so you need to remove the analytics. We don't know how you've installed them, and we don't have access to google to turn off your system at that side. There are no analysis screenshots attached. Could you tell us what the question here for the Atlassian…
-
Yes, you'll need to fix that. You're giving the connection an incorrect login, or JIRA can't reach the server because your network blocks it, or it's not running, or you have misconfigured whatever you have installed in order to make this connection. We don't actually know what you are doing here. When you say "link JIRA…
-
It's usually the board filter, I get that wrong all the time ;-)
-
Your issue does not match the board filter, or it is in a status that the board does not have in a column, or you have enabled a quick-filter that hides it.
-
Did they create a Kanban board instead of Scrum?