Comments
-
https://jira.atlassian.com/browse/GHS-3573 was the first one reported that I know of.project = GHS AND text ~ "column status" Will find you a load more in there, all closed with "not going to fix this" type comments
-
This is a long standing design flaw in the Agile addon. It does not support "move between status in the same column". To get it working, you'd need to re-code part of Agile. Atlassian have said they are not going to do the work to enable this (despite around 200 requests in their issue tracker asking for it) The closest I…
-
In the link I gave, I'd use Robert Mota's third snippet on his answer starting with "using componentaccessor now" as the starting point - that showed me how to create the "map" that needs to be built for the cascading select, and how to push it into the fieldYou do need to think about your translation too. You have a…
-
It's the nature of the storage. The value held in a single select is a single "option". The value held in a cascading-select is a pair of options held in a "map" object. You can only use the standard script to copy values between compatible fields that store the same options. You can take most of the copy script as it is,…
-
No. You're either logged in, or you are anonymous. Of course, you can allow anonymous to "set reporter" and allow them access to your entire user directory, but the point of an issue tracker is to track who does what...
-
How exactly have you configured the notification scheme? Are you using any groups or lists in your user setup? Does anyone else get multiple emails? Is it just create issue doing it?
-
And make sure they are in no groups or roles that grant them access to other projects.
-
I'm not sure there's actually a question here any more, although I admit I must have been slacking and missed the second comment. The answer to the original question (which isn't really much good because the question didn't explain what was being done) is "yes, use a custom field with whatever names you need", Then the…
-
We don't know where you are doing this, so you'll need to explain your setup. As a guess though, you have a custom field with sizes defined,so all you need to do is change the options on it.
-
Follow the route laid out at https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA and you'll be fine.
-
You're in the wrong place (and I'm really not sure how you could have got here with any sane search), this is a site about Atlassian software.
-
I'm not 100% sure of the structure either, but I think the first number (ignoring the 1.0) is the id of the dashboard in the databate, the second the gadget and the third the pointer to the settings. I'd analyse the impact of the gadget first - it may be that there's one particular gadget that's doing most of it.
-
You've sort of answered your own question - as the gadgets are now doing the work on the client, they need to make more requests back to the server to get the raw data to work with. It's not just the gadgets either, there's other places where the system uses more REST calls back to itself. I'm not sure I'd have expected it…
-
You need to edit the .vm files to do that. Bear in mind that I don't know what your "release" field is - if it's a custom field, then bear in mind that your changes will affect ALL custom fields of that type. See https://jira.atlassian.com/browse/JRA-15496 for the requests and links to how-to docs
-
You need to move it to another status - the current one has a "do not edit" flag set on it (this is done in the workflow, you might want to have a detailed look at that - you'll need admin rights for that)
-
You should be able to change the url and then swap it back, but you could have problems. Confluence has caches and indices, so you'll probably end up with a corrupted index (so re-indexing after each change is probably worth doing), and if your confluences have different plugins, you may have some issues with them poking…
-
They won't do anything less "risky", but an Atlassian expert should at least have the knowledge and experience to be able to minimise it Have a look at http://www.atlassian.com/resources/experts for someone suitable.
-
Could you check the documentation that Teck En Yew pointed you to - that answers your question (which is a "No, but there's a workaround") and tells you how to do it as well.
-
You can't on Cloud. Cloud is a managed service and doesn't support any form of "development" setups. You can pay for a system and use it for development if you want, but there's no developer licences. They're for server versions only.
-
No. There's a lot of information at https://answers.atlassian.com/questions/5525/how-to-avoid-issue-edit-conflicts-in-jira
-
The move functionality doesn't support any field edits - it's purely to allow you to move an issue while keeping it valid for the new configuration it might be landing in. It's a minimal amount of process to do one thing properly. You'll have to find or write a new move process that can change arbitrary fields outside the…
-
There are three ways a change of view might have happened * The page has changed - look at the page history * The space theme was changed - ask the space admins * The global look and feel was changed - ask the confluence admins Note that if it is option 3 and you are on Cloud, then it could be a system level change which…
-
This is rather an old question to be commenting on, and I missed the first comment last month. In later versions, the next button will be greyed out until you have a valid mapping - make sure there's a summary mapped to a column that has content on every line. If you've got a project column, check the mappings in there,…
-
Ahh, ok, yes, we're getting there. The problem now is that the sheet you've saved has header and footer information. The importer requires a single line of header (Project, Key, Summary, etc) and then one row of data per issue to import. The safest thing to do is go back to the spreadsheet, and remove the lines at the top…
-
Ok, could you take the csv file and open it in a simple text editor (vi, nano, notepad - not wordpad or anything more clever). No need to change anything, we just want to check the format. Tell us what the first three lines say (feel free to obscure any data you don't want to share - we're interested in format, not data)
-
When you export to Excel from Jira, what it actually creates is an XML file that says "I'm a spreadsheet" to anything that opens it. This is not a csv file, it's xml. When you save a new Excel spreadsheet, it defaults to Excel format. This also is not a csv file, it's an Excel file. Neither of these file types can be…
-
Not directly, but you could find/write a validator that would check it on transitions, and the behaviours functions in the script runner addon might be able to do it on the client side as users enter data (I've not tried that myself, so I'm not sure)
-
If you disable downloads, people won't be able to see the stuff in the attachments.
-
There's a link in the doc that tells you how to upload files via WebDAV
-
I don't understand what you mean. The docs tell you how to restructure and upload a zip to be imported.