Comments
-
Effectively unlimited. Just beware that if you add say 120, and then decide to purchase a licence for 100, you're going to need to disable 20 users to get the full functionality back (I usually remove them before applying the licence)
-
Thanks for sharing your experience - I've seen it hinted at several times, commented, but not really have anyone follow up to confirm that their particular storage was definitely the problem. I was starting to think it might be just that if I was around, NFS or SAN disks would start to shred themselves for no reason other…
-
Ah, I see. I've tried putting the index on several file-systems. Anything other than raw, local, direct access has been an unmitigated disaster. NFS, SAN, Samba - they all seem to put such a drag on the Lucene index, Jira crawls to a halt and dies. Never got to the bottom of it, a simple test of moving the index "the…
-
Out of interest, when you say "NFS hosted cache directories" - do you mean you had the Jira "cache" directories on an NFS drive?
-
That's simply not going to work. If you want to update Jira with Confluence 3.4, you can't go past Jira 4.1 (without risky hacking, and it might be Jira 4.2 is the highest, I'm not 100% sure). I'd suggest you do that jump to the highest Jira first, then take Confluence to 3.5, then you'll be able to move Jira on further.
-
Depends on how you have them communicating. The Jira portlet macro will stop working once you upgrade past version 4.0 of Jira. There are fixes and workarounds, but they're not nice, and it's easier to just go with "incompatible" when explaining it. If you are using the same user-base (i.e. Confluence is reading Jira's…
-
What category is your "waiting" status? To do, in progress or done? Also, do you set a resolution when going into waiting?
-
Yup, and it can be a bit of a pain - if you refer to fields or screens or other ID based stuff, you have to have them the same in both source and target jira. e.g. if source Jira workflow says "use screen 42 on this transition", then screen 42 must exist in the target jira. Some search and replace in the xml can help…
-
I'm afraid not. Outlook had the "group by subject" function removed a couple of versions ago, in favour of grouping by non-standard fields that most applications simply don't use.
-
I'd raise this one with Atlassian support. I've stayed away from Active Objects because of that warning
-
There won't be anything more complex than tables and their indices. Jira doesn't do views, functions, triggers etc, it uses the database more as a slightly structured datastore than a database... You should find that simply dropping all the tables will do the job fine.
-
I think you need to look at what I said before in your system. You'll find a place to write your script when you do that.
-
Ok, decide where in your process you want the issues to be created ("create" from what you've said I think), go to edit the workflow and find the "create" transition. On there, add a post-function and select the scripted functions. There is a built-in "create subtask" script you can use there!
-
There's two questions here. For "template projects", you could write an add-on that provides a project template and embed code in that to automatically create a set of issues. For "template issues", you could find or write an add-on that provides a post-function that can create issues, and tag it into the create issue…
-
No, Jira doesn't have global/shared components. See the request at https://jira.atlassian.com/browse/JRA-8663 for lots of ideas and suggestions.
-
Open up the application server installation in a file manager, find the template files that render resolution, and change them to forcibly add the "none" to the list. Do this while JIRA is offline of course, and keep a backup (i.e. do it in test first and check it works). The file used to be called resolution-edit.vm, but…
-
Paul is on Cloud at 6.4, so I assume it's a new function in there, but I don't have one to hand where I can check. Like you, the 6.3 I'm using at the moment still behaves the way I described in my original answer.
-
Because you couldn't do that at the time the question was asked.
-
The resolution field handling is a legacy kludge in my opinion. I'd have redesigned it in Jira 2 if I'd been the product owner.
-
Technically, it's not "mandatory" in Jira speak. The field is optional, otherwise you'd have to have it on the create screen, which would be pretty useless. Your problem is that when you do place the field on a screen, it does not have an "empty" option, and defaults to the first value in the list, so you always end up…
-
Yes, you can run them on the same url with different contexts. It's usually easier to do this by running them behind a web-server that proxies them (doesn't matter whether they're on the same machine, ports or anything else if you do that). Most of us do it with Apache.
-
Ok, so what do you mean by "transfer"? If you just want to move the type to another Jira installation, you just add the new type. If you want to use the type in a project where it doesn't already exist, change the issue type scheme. I suspect it might be something else though...
-
What do you mean by "template"?
-
I'm afraid not - languages are installed as server-type add-ons, which can't be added to Cloud by the end-user.
-
It doesn't (unless you've got some odd setup). Every issue in JIRA is an individual issue. If one is a subtask, it still is an issue, it just part of another issue as well. So ABC-123 could easily have subtasks ABC-456, ABC-235 and ABC-321 Is that not what you are seeing?
-
Ah, no, most reports will give you basic numbers as a count of issues. For adding up points, you'll need to be looking at the sprint gadgets and reports.
-
You don't. JQL is for finding issues, it says nothing about what data is on them or how it's displayed. All you need to do is take your search and display it in something that will add up the numbers for you. A pie chart, working off "assignee" will do that automatically.
-
I've never managed to get around this problem without code. We specifically write a derived date custom field that would store/display/search on "first monday before updated field" so we could search for "everything touched last week". I think Jira 5 may have some JQL clauses that help now though...
-
er, it's "updated > -Xd" - pretty simple jql, generated by the simple search (which has a nice popup help box to walk you through it) or typing in the JQL box.
-
We can't help you here - you need to talk to Atlassian, via support or the contact us that @Jim Conaty gave. He will have been emailed your updates here, so he might be able to chase up the support request you've raised as well.