Comments
-
You can create any select-list field you want to work like resolution. But you won't get to use it in the burn-down chart. The burndown reflects things that are done.
-
No and yes.You do not need to worry about it appearing in the "wrong" list on your current installation. Technically, it is a user-installed plugin because you did it by hand, but the difference between system and user plugins is not much more than "it came in the installation off-the-shelf"However, before you upgrade, you…
-
Upgrade to 6.3.7 is the official answer, but if you have a look in the comments, you'll see a link to a new .jar you can download. Download it, then use the plugin manager to "upload plugin". I would keep a copy of the .jar from your current installation just in case, but I'm always cautious.
-
It's not a bug. The point of JIRA is tracking stuff, not obscuring things from users. The structure to hide bits of a task (i.e. it's subtasks) simply isn't there. Florjan's workaround is clever, but it's not going to work everywhere because JIRA doesn't want to hide this data - it's very nature is to show the users all…
-
There aren't any. JIRA doesn't use SOAP internally, it's for other things to talk to JIRA. If you've written something that does use SOAP internally, that's fine, but you'll need to track it down manually - JIRA's SOAP service simply listens and responds. It has no idea what might be using it.
-
They are treated as stories, stories are supposed to be on the board. They're not Epics. Did you have a look at swimlanes? I suspect your best option would actually to have swimlane = story, they're correctly on the board then, and let you manage tasks within them.
-
>Now, on various boards, we have stories as well as tasks appearing together that increases the count of overall incidents unnecessarily whereas we are interested only in looking at tasks for tracking purpose. That would make me say simply "change the board filter to say 'and issuetype = task'" which would drop the stories…
-
One of my old clients recompiled it for 4.4, but I can't tell you how much they had to change the code for the new APIs
-
Yes, go to General Configuration -> Collaborative editing, and set the level to "off" This will basically put the editor to working the same way 5.10 did (which in terms of RAM and networking is pretty much the same as 4.3)
-
See https://confluence.atlassian.com/jira/migrating-from-jira-cloud-to-jira-server-299569790.html and https://confluence.atlassian.com/confcloud/migrate-from-confluence-cloud-to-server-724765578.html
-
Just to be clear - I don't know if there are duplicates, that's just one possibility that I know can cause odd things to happen. This is a difficult one because you don't seem to be able to see the two broken accounts. Do you know anything about them at all (in Jira terms, I mean). I'm going for the login id because that's…
-
Mmm, that's actually consistent with duplicates - the navigator falls over in most versions I've used, but in others, simply returns the first user ID it finds. Can you establish what the broken user IDs actually are? Then visit their profiles in Jira to see what groups they're in?
-
Sorry, I could have been more clear. If you list out all your users from the database, do you have any duplicate login ids? Or, as you're using AD, people who have an id in the internal Jira tables and a duplicate in the AD? (The login is the unique string you can see on a users profile at the top left - in older versions…
-
Do you have any duplicate IDs in the database? Are the users from different sources?
-
You can export the results of a filter. But there's no other "partial export". If you want a whole project, you have to export everything.
-
Ah-ha! I think the 3rd screenshot explains it. I would expect you (Assuming David = DavidK) to be able to create and view issues. But I would expect Brian to be able to create issues, and then not be able to see them after he creates them. It's the "browse projects" permission in the "project permission" section. It's not…
-
Ok, that's sort of good - you have set up everything correctly. Only thing I really missed is that on line 4, I should have said "check the 'browse' line most carefully" - not too worried about the others, but 'Create' and 'Browse' are the important ones for this question. The check here is not quite that they are the…
-
No, permissions are all project related, nothing to do with groups. It sounds like you have everything set up correctly, but I'd go over it VERY carefully. I.e. * User is definitely in the group users_ProgramA * The group users_ProgramA is definitely in the role of Project_User, in ProjectA * ProjectA is definitely using…
-
Start with https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA I always recommend reading ALL the release notes for every mid-level version you will be jumping (i.e. 4.1, 4.2, 4.3, etc)
-
It makes sense, I should have thought of "importer looking for the wrong licence type" as being a possible problem when @Jim Hackney was able to confirm Software was enabled and working fine!
-
Do you mean in Pivotal, or in the Pivotal importer add-on?
-
You might have tried it and not bought it, then not removed the add-on!
-
It's a bit of a poor failure, but what's happening here is that the importer is seeing that Agile is installed and hence trying to write some of the incoming data into Agile related fields (I have a feeling it's the ranking, but I'm not sure). Then, as the add-on is expired, it's saying "nope", and failing unhelpfully,…
-
No, we are not OnDemand support, we are end users like you. If you can't find your admin, then you will need to contact support to get yourself back in.
-
If you have lost your admin rights on a Cloud/OnDemand Jira, then one of your administrators has removed it. Start by talking to your other admins.
-
Again, no. Although you might try the behaviours plugin, which uses javascript to modify on-screen options.
-
No. But you can do it with workflow properties (and workflows can be defined by project and/or issue type) Have a look at https://confluence.atlassian.com/display/JIRA/Workflow+properties
-
We don't know which Bitbucket server they are talking about, so we can't give you a url.
-
You don't really want to do it - that's why Jira doesn't do it. If your users leave a field blank at creation time, then why would you encourage them to accidentally set it during an edit? It's blank for a reason. If you do this, you'll find a LOT of your issues suddenly have defaults splattered all over them when you…
-
Ok, that means they're working. Thing about a default value is that you only want to default it on issue creation. During an issue edit, there is an existing setting for a field, even if that setting is "empty". The users have deliberately chosen that value, and you do not want to have a default override it. So default…