Comments
-
That does look like it is being added by an add-on, but that's not quite what the docs say it behaves. Are you using the correct version for your JIRA version?
-
I thought I'd mention the plugin, just to rule it out as a possible candidate. It's not bundled into 5.1
-
The disk space should be quite easy to monitor actually - most of the time, if you blow the disk space out, the import (and Jira in general) will litter the log with "can't read/open file" type messages. Sometimes it won't be too quick to do it, when the log is on a full disk, but generally one line of log is much smaller…
-
For what it's worth, I wouldn't even try to run Jira in less than a Gb of memory. Although I'd expect it to be ok-ish with 768Mb and only 5000 issues
-
You've sort of answered your own question - the document you point to covers the technical side of how to export more (and why it's a bad idea). I think the missing piece for your question is that OnDemand is set up to enforce the hard 1000 limit to prevent the overloading caused by large requests. You can't change that on…
-
Not really. The usual way to do it is https://confluence.atlassian.com/display/DOC/Modify+Confluence+Interface+Text but you can't do that on Cloud/OnDemand.
-
You can use the file:// url prefix to do it, but it won't do what you think. Your R:// drive exists on your client machine - it'll work for you, and fail for all other users that don't happen to have exactly the same drive mapping.
-
JQL is for finding issues, not returning the information on those issues. If you're trying to compare it with SQL, then the best way to think of JQL is that "it is only the where clause". There's no "select what", it's just "where" and your report or display is reponsible for selecting what to display. To fetch only…
-
Bother, I thought it was trapping scheme edits too (not the users/groups, but the "add new level" and "change rules for level" type stuff) Sorry.
-
I'm really bad at memorising the admin menus in different JIRA versions. I think it's Admin -> System -> Audit log, but if not, then it's definitely called "Audit" something, so a search in the admin section will definitely find it.It logs a *lot* of admin actions - you'll usually see patterns like "lots of user changes"…
-
There's no way to stop the administrators changing things, as that is their job. Essentially, you have to trust someone to look after your system, and that's what your admins do. You should have a small team of people that you trust running JIRA. (And enable the admin logging so you have some trace of what they've been up…
-
Difficult to say. Doc files are working fine for me in 5.7, so the question is what's different about your installation, or the file you are attaching. What does the log file say is going wrong?
-
Yes, I know corporate paperwork can be a bit of a pain (one of the reasons I took a break away from them was the burden of broken procedure). But you can understand that someone who writes software would want paying for it and hence need to remind people to pay until they do.
-
No. If you don't want the banners, then get the licence now, you don't need to wait until the end of the evaluation.
-
Not if you're using OnDemand. Standalone users have this option: https://developer.atlassian.com/display/JIRADEV/Customizing+Text
-
What sort of help?
-
Yup, issue updated. Move is for "move from project A to B" or "change issue type to a radically different one"
-
It's not even a "migrate". It updates the data without moving it (unless you upgrade a copy of the system rather than the original)in if we upgrade the Confluence/JIRA from 6.4.4 to the latest server version of Confluence/JIRA, than do we need to migrate the content from Server Version 6.4.4 to the latest version of Confluence/JIRA version? or is it that we just need to upgrade the Comment by Nic Brough -Adaptavist- August 2016
-
On Server, you can add Service Desk to JIRA 6.2 or above (in fact, lower as well, but there's no point looking at older versions really). On Cloud, the version is irrelevant to you - it's maintained at "latest Atlassian version", you have no choice of versions
-
Yes, you are completely right. A load of stuff changed in JIRA 7, although the main things for most of us were "two add-ons became applications, and there are now three initial starting downloads instead of one" On JIRA 6.x, if you want to add stuff to it, it's all add-ons. On JIRA 7.x, you need add-ons or applications. As…
-
At a guess, you're not yet on JIRA 7?
-
Yes, JIRA 7 changes the structure - Service Desk is no longer an Add-on, it's an application.
-
I'd install Jira-Software, run it and then go to "manage applications" and add Service Desk. Use evaluation licences until you're certain you've got what you need
-
I'm not sure there's a lot on hacking the core of Jira around - you need the source code for a start!https://developer.atlassian.com/display/JIRADEV/JIRA+Plugin+Development is a good starting point - although I've said you'll need to hack the group-handling code, it may be possible to do it with a plugin. The principles in…
-
There's nothing in JIRA that can do this - you'll need to hack the core group-handling code to fire events. You could try to hook in the same way the audit-log functionality does as well.
-
I forgot - there's a minor problem with scripting this. If the members of the group are changed, the results of the scripted field will be wrong until the issue is re-indexed (i.e. project re-index or any edit or transition on the issue)
-
That's a perfect use-case for a scripted field, and almost one I've done myself quite recently. The group-picker I used was a single select, and they specifically wanted just the user names as a long block of text, but the code below should get you started. import com.atlassian.jira.component.ComponentAccessordef…
-
JIRA has attachments, this plugin just makes it a bit more specific for working with images. So * Yes * They stay attached to the issues * It might work fine, it might work partially but have bugs, it might stop working entirely
-
Have a look at https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions
-
There isn't really an "archive" function, but most of us set up an "archive" permission scheme and apply it to the projects we want to archive. That scheme is usually set to say "no rights except browse", and if you make the "browse" limited to just the admin group, or even leave it out at all, the project and its issues…