Comments
-
The ability to use a transition is controlled by the "conditions" on them. Not the permissions. I find it better to think of permissions as "a set of flags to be used in other places, such as conditions (so I can say "only people with close permission can use the close transitions" ) ".If you have anonymous users able to…
-
Yes, a support request would be better.However, they are going to go into a lot of detail with your config, so it's worth trying to explain the complexities up-front.
-
I'd also add that in Jira 6.3+, there is a new permission called something like "Can use transitions".This fixes the default "anyone can use a transition if they can see the issue" problem so you don't have to worry about it any more. Despite saying that it fixes it, I would still STRONGLY recommend that you think about…
-
Pretty much a "no", it can be very hard to downgrade an Atlassian application. 5.9 Server is on the way, your best bet is to wait for that, migrate to it and then bother the add-on vendor to update as well.
-
Ideally, use roles in all schemes, then to "see all groups associated with a project", you can just look at the role membership screen for the project.
-
The attachments path was fixed in an earlier release of JIRA for security and sanity reasons. You can't change it easily. The standard recommendation is to use directory mapping or links to say "when I use my <long path>, actually read/write <somewhere else>" at an Operating System level - JIRA doesn't really care, it…
-
Samir, you've asked this twice before https://answers.atlassian.com/questions/876/manage-automatic-assignee https://answers.atlassian.com/questions/846/automatic-assignee Both of those conversations have valid answers, but you've simply repeated the question again on one of them, and asked a different question on the…
-
Sorry, but I am right. Users who can not see an issue in Jira will not be emailed about it. You've worked around it in AD, because those users automatically have browse, but if you remove that, they won't get the emails. There's the workaround that makes Jira send emails to groups that the users happen to be in, but that's…
-
Simply put, that is not going to happen without code, or non-ideal configuration If a user cannot see an issue, then they will not get email about it. End of story - and correct design I should point out - emailing people with stuff they can't see is a security loophole, so you *should* have to work hard to break the…
-
Not off-the-shelf, but there's a simple setting that enables exactly this facility (Atlassian use it in their support project). See http://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission - it's only disabled because it's possible to break Jira if it's misconfigured, so they disable it to…
-
No, that level of delegation is not yet available in Jira. See https://jira.atlassian.com/browse/JRA-3156 for the request and some conversations.
-
See https://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email
-
There's a big question here - is the target JIRA new or is this actually a "merge" process? (As in, you're already using the target JIRA and have data in it you want to keep) If your target JIRA is a new system, then it's easy - see https://confluence.atlassian.com/display/JIRA/Migrating+JIRA+to+Another+Server If it is a…
-
I'd recommend 6.3 over 6.1 - more functions, more improvements, more bug fixes, etc. Data loss - no, you won't lose data if you do upgrade as per the upgrade guides in the docs. Functionality loss - not really, but you should read the release notes for 6.0, 6.1 and other major revisions to see what changes and what gets…
-
I'm sorry, that does not make any sense in English and it mixes up too many concepts and words for me to begin to guess what you might mean by it. The best guess I have is that you want to change the assignee of an issue in a post-function, but you have added the word "validator" in the middle of your list of words and…
-
Agile Minutes is not a Cloud add-on - you can't add it to Cloud instances.
-
I'd say you're doing the right thing - consolidate the fields you can, see if there are any you can remove completely, and remove searchers for fields that don't really need them. With 100 fields changed, I'd expect to see some improvements in some areas as a result.
-
Yes, setting searcher to none will help on the indexing side. Removing the custom field will do a little bit more, as it removes the overhead of looking after the field too. But my instinct is that the overhead of an individual field is fixed, and relatively small. So deleting a text field and deleting a select list will…
-
It's hard to say. You'll get some performance increase from removing each searcher, but whether your users will notice removal of one field is unlikely. If you removed 20 searchers, you might get noticed a bit more. It very much varies by type of field too. As you've picked up from the docs, single select lists have much…
-
You can't do "screen per user", it's "screen per project" (and actually, issue type). You're in the right place though - the screen schemes control this. * So, assuming you have screen 1 and screen 2 that you want to use for creating issues... * Create two screen schemes. One should say "for create screen, use screen 1"…
-
This is more of a networking question than Confluence. But. Your server has an ip address, which other systems can use to send it stuff over a network. You need to set up your network so that there is a route from the outside world to that server that machines on the network can use. BY default, most places will firewall…
-
Have you moved issues from the projects included in the board into the non-board projects?
-
I've not seen a proper "how to" on using Jira as an inventory system, but the usual starting point is to decide exactly what you want to track, and map that on to an issue. I've used it a few times to track "assets", the usual one being servers. Each server is a single issue, usually with the host name as the summary.…
-
1. Nope, and 2. Not really. You could try to rig up some complicated request/workflow/post-function-hack, but however you approach it, you're going to need some coding that bypasses the "only admin can change this setting" thing. Having said that, I've generally found that bottlenecks in Jira administration are only really…
-
Not a lot. If you had the backup services installed (they're on by default), then you should have .xml files in the applications home directories, so you could install new versions of them and restore the xml - you'll need the attachments directories too. But that's about it if you've lost the databases - you're mostly…
-
Nancy, yes, although the large installs I've used were all on 64bit JVMs already, so I can't really tell you that that improves things.
-
Sorry Jamie, yes, I'm 99% sure that's where I got the idea from in the first place!
-
I've been there too. Given decent hardware, we racked it up to 500k without problems, in quite a complex install. Your main problem is likely to be load induced by users - if you have a lot of them, and they're doing large reports you're going to get problems (or more to the point, inefficient ones - exoorting filters over…
-
It looks like you are using Cloud JIRA? Where you can't install this type of add-on, so there is no "upload add-on" option.
-
What url are you looking for? "fits the plug-in" doesn't tell us a lot.