Comments
-
Have a look at Admin -> Global Permissions -> Who can browse users to begin with. If your user is definitely in one of those groups, then can you check for any errors as he goes into a screen where assignee is editable, or when he clicks "assign issue", and check the logs for warnings and errors as he does it.
-
Make sure they are both running by checking their front-ends, then have a look at the processes running on the server. If there are two Tomcats running from different directories (look for the directory names in the process information), then you have them separate. I'm almost 100% certain that you have them separate. The…
-
You need to check the "global permissions" to make sure your account has the right to "browse users"
-
> Killed (core dumped) That pretty much says Jira is being killed from the outside by something else. If it were Jira falling over and creating a core dump, you'd have a load of other stuff going into the log, and almost certainly nothing saying "killed". I'm afraid you need to look at what your root users and operating…
-
Unless you've got a good grounding in the Jira API and the script runner plugin installed, you're probably going to find that doing this by hand is going to be quicker than learning everything you need. The script runner would at least allow you to convert 300 lines of "name of customfield" to 300 lines of "amend relevant…
-
No. It will change if you move it to another project, but just changing the issue type will not affect the id/key
-
You won't get system-admin rights - that's restricted to Atlassian support. To get confluence-admin granted in the case where your existing admins have left without granting it to you, contact OnDemand support at support.atlassian.com
-
I've always been able to use Tempo, so I've not looked for other plugins, so I can't really say, sorry.You'll need to dig out all the screens that the worklog description could be placed on and add the script to them, hacking the core of Jira to do that.
-
Mmm, I wouldn't try to do that on the screen - it needs javascript, which you'd need to inject in more than just that screen, and if a user really doesn't want to do it, it's a doddle to bypass it.You want to do this server-side with a validator of some sort. I know the Tempo addon can make a worklog description mandatory…
-
So what do you want to do to the "log" button?I ask because you can customise some things without touching the template files...
-
No, there isn't. The screens in JIRA are almost all dynamically built using templates (using webwork and velocity mostly) and it's often not as simple as "tweak one file", some screens are constructed from many. There's little or no plain html in JIRA. Question is what exactly do you want to do to the screen? Your…
-
Natively, no, the javascript produced by JIRA generates html that acts as the slider/tab/pop-up (not sure what the right phrase for it is) But there's nothing to stop you creating your own form that uses REST to send data over to JIRA, much the same as a collector, or even sending what a collector would when used.
-
It can help with the identification. If you have a workflow *for the sub-tasks* that goes something like "open" then has "closed" and "can't do it" type status, you can show the sub-task status on the parent issue. You could also just show the resolution on there too.
-
It might be useful for some ways of working, but most people would still regard "can't/won't" as resolved. In fact, most of us would do that with the workflow if we needed to have that ready identification. Not because it's the wrong thing to do (it is not wrong), but because JIRA does not do that. The whole of JIRA is…
-
No, sorry, when I said "it doesn't matter", I meant in the code.JIRA does not care what the resolution is, just whether it is set or not. If an issue has a resolution set, it is done. That's the end of the story. You could have a resolution called "unresolved" if you wanted to and that would still represent a…
-
I'm afraid not. The flag is very simple - a green tick for "you don't need to worry about this any more" if the resolution is set. Doesn't matter what it's set to, it's resolved, so it's done.
-
I think you're posting in completely the wrong place. This is an Atlassian customer forum/help system. Nothing to do with DMCA complaints.
-
A complete guide wouldn't help you here. You need to read the error messages it is giving you to find out what is wrong. You might also want a look at https://confluence.atlassian.com/display/SOURCETREEKB
-
You need to give it a path on your machine that * exists * is fully read/write enabled for the current user * supports the structure of the repo you're cloning (rare, but if you're using an odd file system, it might have strange restrictions on directory names or something) Note that you've got an error on the source path…
-
By "open", I would say you mean "create new project"? If so, yes, you will need an add-on or code to do it, as it normally requires admin permissions. There are some add-ons that can help you delegate the rights. A simple script is a little more difficult though, as project creation involves creating, copying or reusing a…
-
Your permission scheme for the project needs to allow you to "maintain watchers" Once you have that permission, you can add anyone you want as a watcher.
-
No. The whole point of these labels is that they're easy to define and mean the same thing. There is not really any difference between human and Human when you're searching or categorising stuff, so Confluence takes a simple consistent approach of sticking with lowercase throughout.
-
That's correct, although I think you mean labels. The whole point of these is that they're supposed to be single words, or you can't do useful searches for them. Anyway, try the underscore instead of hyphens or spaces - the labels recognise _ as characters in words.
-
Presumably the same question as https://answers.atlassian.com/questions/35751193
-
Successful changes to issues are recorded in the issue history not the logs. Look at the issue history for the changes.
-
There you go, it's running fine. In fact, it's responded with a setup page, so there's no need to look at the application log as that tells you it's working - your problem is with your browser not connecting. You'll need to fix that.
-
Telnet isn't the way to test it - try a wget or curl and check that you get some html back. Although, the "connected" message alone tells you that it is running and listening. If it wasn't running, you wouldn't connect. You should read the application log to see what it's doing - <jira home>/logs/atlassian-jira.log
-
No idea - "cost rate" and "MD" are meaningless in JIRA speak - you'll need to explain what you've set up and what they are for your users.
-
Getting it running with http is exactly the right thing to do as the first step, as it means you know it's all working and whatever you do next to make it https is the problem if something goes wrong! Move on to https://confluence.atlassian.com/adminjiraserver071/running-jira-applications-over-ssl-or-https-802593051.html…
-
Right, that makes sense. For an issue to be seen as closed by a sprint, it has to be in the right-hand column of a board. Your closed and resolved issues, and the ones that have sub-tasks that are not done, are moved to the new sprint because you've told JIRA they are not done.