Comments
-
How are you defining the clients? Different instances of Jira (you need to log into the other instance)? Different projects in the same Jira (you need to talk to the administrators to find out what new project roles or grous you need to be added to)
-
In theory, yes. But I would very much recommend testing it carefully, as sometimes the config and/or plugins fall over and it's worth going through an intermediate version 5.
-
You will want to do this in steps (3.unknown -> 6.3 is NOT going to work), and follow the documentation at https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA There is not a lot more we can tell you - you need to read the documentation, plan the steps of upgrade appropriate for your site and test it.
-
The issues you are cloning from will have had the field filled in, so the clone process copies it.
-
You have a field called "access" that is not on the create issue screen, but is flagged as mandatory in the field configuration. You'll need to add it to the screen, make it optional, or remove it from the project (Best option is probably a new field configuration where it's optional)
-
Technically unlimited. In theory, you could whack in gigabytes of text.
-
I don't understand. You said you had used some css and javascript to remove the save button, then you said you wanted to see it again. So you need to remove the css and javascript you added to hide it.
-
Remove the css and javascript?
-
I think you need to give us a bit more information on your question.
-
It looks to me like you have a broken add-on, but it's hard to tell from that chunk of log - are there any other errors? You should be able to restore your data from that backup file, yes.
-
What does the log file say has gone wrong? <JIRA home>/logs/atlassian-jira.log Also, have a look in <JIRA home>/export - are tehre any files in there? (It should have regular backups in there)
-
You can't really do it, the point of the "all" is that you can use it from any status. If you're determined, then delete the "all" transition, and create a new one for one status into closed. Then you can reuse it for all the other status -> closed transitions
-
What column are they in on your scrum board? The resolution/strikeout doesn't really matter when it comes to ending a sprint, the question is what column they are in.
-
You probably need to explain your TLA VAR (Unless you really do mean Voltage adjusting rheostat?) JIRA doesn't do that in the way most people mean it, but there are a couple of options. Y ou can easily make fields read-only by removing them from the edit screens and moving their updates into the workflow and allowing only…
-
You don't. Permission schemes are handled at a project level, not issue. Two options both involve using the workflow to do something differently for the issue type. One is to do something quite sneaky with hidden fields and the workflow for that issue type, but it's really hard to get right and you need scripts. The other…
-
Duplicate of https://answers.atlassian.com/questions/37522613 (which is answered)
-
On the create screen, it only appears when you've started to enter data that *might* be lost if you change the issue type at that point. Which would aggravate the users if they aren't told.
-
Which does encourage your users to bother your admins saying "why can't I change to type X"? I'd very strongly recommend NOT implementing that.
-
It's warning you that there are issue types you can't change to using the type as a field. The simple way to be rid of it is to remove the issue type field from the create and edit screens. Or, you could configure your issue types in the project to all work the same (although I doubt that's useful to you, most people have…
-
As well as Jobin's "pull", you can use emails on events to trigger actions in other systems. That does rely on the other system being able to read and process the emails Jira sends though
-
Ah, hang on, the "edit" property is separate from the "make comment" property. The "edit" property is stopping you from editing. If you want to block "add comment", then that's not an edit, and you need a different flag. I've got: jira.permission.comment.user : denied jira.issue.editable : false
-
That absolutely proves it's the client side - Cloud is definitely just handing files over to the client, there's no "windows 10" involved on the server side.
-
Oh, great, Windows error messages that tell you little or nothing about the actual error. This is going to be hard to diagnose, but it's likely that the Office Connector is serving up a file, and there's a network or Windows problem preventing Office from opening it. I'd want to read the log file on the server to see if…
-
It is supported on Windows 10, and Firefox as long as the WebDav addon is installed. What problems are you having here?
-
Hmm, I used to use -sales at atlassian dot com-, but I've not needed to try it for a while
-
Number of times, no. But it's all date based. If you go over a month, the system will reduce it's functionality until you put in another valid licence. If you need to extend, you can get in touch with Atlassian sales - they're quite friendly about extensions
-
Yes, the evaluation license gives you a fully functional system, for a limited time.
-
Please bear in mind that if you delete files from the disk, Confluence will not be aware of the deletion and will report that the files are still there, and then break when it tries to use them (not crash, but you'll get broken macro displays and errors if people try to open/edit the missing files)
-
There's no real reason to remove it, so I'm not sure why this is an issue. If you don't configure it to connect to any hipchat server, it doesn't do anything. Might be better to explain what you are trying to fix by removing it.
-
You'll need to change code in the core of Jira - those filters are effectively hard-coded in there (although I think it's actually in xml files, it needs compiling of one form or another)