Comments
-
That's a good answer, but you'll need to check versions. I don't think the versions of Greenhopper that allow this work with the version of Jira you're on - you'd need to upgrade
-
(Caveat - if you have no Linux people to look after your servers, then use Windows. Use Linux if you genuinely have a free choice)
-
I'd like to add - use Linux. It works far better than Windows. I once got a performance increase of nearly 20% (tested on bulk operations and slow page loads) by swapping a JIRA installation from Windows 2008 to a CentOS install. The hardware was identical, and the servers in the same rack.
-
The Table Grid editor might be worth a look too - see https://marketplace.atlassian.com/search?q=table+grid
-
Ok, that's nice and clear. The lists are limited simply to avoid cognitive overload, but if your humans need a really long list, you have the option of editing the code that is limiting the list. The data is all there, you should just need to tweak the .vm file that is only showing you the top part of it.
-
Could you explain the problem a bit more? The best answer I can give depends on whether it's a "human wants to see the whole lot" or "I'm coding a plugin/script and need the list" or "I'm doing something in javascript"
-
Ah, you didn't say OnDemand, or I'd have mentioned that. However, OnDemand DOES have the Jira Suite Utilities installed, so you should be able to add your validator right away!
-
You haven't gone wrong. Jira has a very simple approach to mandatory fields. They are either mandatory and have to be filled all the time, or they are optional. Screens and workflows are utterly irrelevant to this process. What you need to do is find or write a plugin that implements a "validator" for "this field must be…
-
You may loose some functionality, as the two applications will now have separate user directories. You may need to recreate the application links in both directions too, as the server on one end has moved. But other than that, no, it should be fine.
-
You have to set the visibility as it is logged - see https://confluence.atlassian.com/display/JIRA/Logging+Work+on+an+Issue
-
Ah, I see. I'm afraid my French is very weak, and I missed the time element.You can hide worklogs in JIRA, similar to the way you can hide comments, but you cannot hide the "Estimates" area which show the totals and all the summary data is available in reports. I think the Tempo plugin has some stuff about hiding and…
-
JIRA doesn't have any reporting restrictions really - if you can see a project, you can see all of the related reports, dashboards and the issues within it. You do have the option of issue restrictions within projects, where you can hide individual issues too, and reports and filters will ignore them when run by users who…
-
I think you need to explain what you're trying to import from first. Assuming it's CSV, start with https://confluence.atlassian.com/display/JIRA/Importing+Data+from+CSVwhich covers sub-task imports. If it's not CSV, it could be anything and you'll need to explain.
-
It's because it's not really a tree structure - each "space" is a collection of pages. That's it. They have to have unique names because there isn't a tree behind it. Atlassian have said they're not going to change this approach - https://jira.atlassian.com/browse/CONF-2524 In your case, I'd think about inverting the…
-
Sorry, I forgot, but your screenshot reminded me - you also need to check the "conditions" on your workflows. If there are none, then anyone can go through a transition anonymously. Add conditions to prevent this.
-
The answer you refer to is still correct, and there's not a lot to add to it - you have allowed anonymous access, and someone has used it (either in the UI or via a script or post-function) It's too late to "see the user names as before", the comments made are not tracked, because you allowed it at the time. If you have…
-
Check that the notification scheme says to notify watchers on the updates you want them to see
-
By default, add-ons log to the main application log file.
-
Yup, I can't argue with that. I've worked with Jira for many years, and there's obviously a huge gap between "project admin" and "system admin" that needs fixing. If it's any encouragement, Atlassian *do* revisit old issues and fix them. Sometimes. I've been whinging about "can't rename options in select list" for years,…
-
No. Project admins can amend users, components and versions. That's it. You probably want to have a quick read through https://jira.atlassian.com/browse/JRA-3156 and vote on it! (Please? It's really needed for, well, everyone I've ever worked with. It's #3 on my list of things Atlassian need to fix, so every vote is…
-
Unlikely, if your current data has a valid Deve/Test licence installed already, than that should travel with the data as it upgrades. I'd still get hold of the Atlassian account though - just in case!
-
That's excellent news! I was struggling because your combination of version and symptoms wasn't adding up.I'm not sure I understand the fix, so I'd really appreciate it if I could paraphrase it all and ask you to confirm or correct it?You have a user who is missing fields on the create/editAt some point in the past,…
-
1. Look at the backgrounds of the screenshots - the users have popped up the screen from two different places.2. It's a hack - https://confluence.atlassian.com/jira/how-to-hide-the-configure-fields-button-on-the-create-issue-screen-317950124.html3. Look for the Script Runner section in Admin, the Behaviours would be below…
-
What happens if both people try "edit" from the same place? One of these is from the navigator, the other the issue.That shouldn't actually matter though. It really does look like you've got the Behaviours addon running, and someone has turned off the configure fields ability (after the first user hid half their fields)
-
The problem is that JIRA simply does not do what you are seeing - all users see all the fields you put on an edit screen. The configure fields button always appears for me, so I'm not even sure where you are looking now.There are a couple of exceptions - you won't be offered assignee or reporter if you don't have the…
-
What version of Jira are you using? The configure button will be there in more recent versions.Also, have you checked your addons? Do you have Behaviours or Field security for example, or others that might be hiding fields?
-
Go to an issue, click "edit" and look at the top right of the popup for "configure fields"
-
There aren't any fields in JIRA that behave like this, unless you've got an addon. Could you confirm that this is happening just in edit mode? They can see the fields in issue view when they have data? (If it is just edit/update, look at the "configure fields" option where a user can hide fields if they want)
-
See https://confluence.atlassian.com/jirasoftwarecloud/creating-issues-using-the-csv-importer-764478441.html
-
It's a little unclear on what you want to do here. If you want to get a file from JIRA, run a search for the list of issues you want to get out, choose the columns you want to see, and then, in the issue navigator use "export to CSV" and open the resulting file in Excel. If you want to import stuff into JIRA, then create…