Comments
-
That sounds like you are creating tasks rather than sub-tasks. How are you initiating the "create" process when you create the issue?
-
How, exactly, have you granted this permission? Did you use the right group in the right permission scheme for the project?
-
You can still disable them in the application - that's not a flag in LDAP
-
Have you disabled them in the JIRA interface?
-
You can use the Tempo REST API, but the worklog stuff is available in plain JIRA, so you don't need it for that.
-
Um, Tempo doesn't actually log the time spent - it adds features on top of, and alongside JIRA's time logs. For total time spent on a story, or by user, read the work-logs in JIRA.
-
For Cloud, the path is simple - get a Confluence Cloud added to your account, then create a knowledge base space (or spaces) in it, and then go to the JIRA project(s) that will need the KB and link them to the spaces
-
Because the gadgets are not strictly part of Jira. You can use them in other applications. To support that, they have to have their own code for some things, and inherit as little as possible from the application they are running in. If you want to change gadget styles, you either need to work out where they're getting…
-
On Cloud, no. You will not get access to the database.
-
I'd point out that just sending the email is a security issue if it's going to an untrusted person. The content leaking is "closing the stable door after the horse has bolted"
-
Yes and no. The users are added to all groups that have "Jira user" global permission. This allows them to actually log in and your user needs to be in one of them What most people need to do is decouple groups that say "can log in" from ALL permissions. The usual approach is to have "jira users" able to log in, but remove…
-
Look at the permission scheme for project Y. It will say things like "Create: group of users, or users in role", "Edit: reporter, assignee, group of users", "Move: project lead, system admins". And lots more. Once you know what roles or groups the user needs to be in, amend their account to match (if it's roles, then add…
-
Hmm. That looks like it's due to a plugin (one that ties versions and components together). Do you have https://marketplace.atlassian.com/plugins/com.deniz.jira.versioninginstalled? If so, I suspect the problem is in that Also, can you check the project components - basically, does it have any at all? If not, then does the…
-
Ah, yes, you have to set up a log object for scripts import org.apache.log4j.Category def Category log = Category.getInstance("onresolve.jira.groovy.GroovyListener") log.setLevel(org.apache.log4j.Level.DEBUG)
-
Yes, the "issue event" the listener picks up will contain it. From memory, you should be able to use just "event". So event.issue.getCustomFieldValue(field).toString(); The bit I am a little more hazy on is setting the value. I think you need something like the post-function code for amending a field: I've called the…
-
I said listener.
-
JIRA Software's board only recognises the timetracking and standard numeric fields as valid estimation statistics. A script runner field is not a standard numeric field, so it won't see it. You are, however, spot-on with your idea. Create a normal numeric field, place it only on the issue view screen (not create or edit),…
-
Yup, as I said, copy it into your own code.
-
It can't - it's providing a context and reusing a file. It's not rendering it without a context as you seem to be trying.
-
You can't really do that. A .vm file requires a "context" which is provided by the code behind it. You can't just take a .vm and render it from elsewhere because the context for it won't be there in your code. You can, of course, create your own context for a .vm file provided elsewhere, but you might as well just copy the…
-
The top-right cog will also appear for project administrators, but only take you to projects you have admin rights to. There's also System administrator rights, but they are a wider set of options than the JIRA Administrator, appear in the same place, and simply give you longer lists of things you can change. You also do…
-
Karma is what we get for being active (and hopefully useful) here on answers. I'd ask a proper question instead of commenting on a 4 year old thread that isn't really much to do with your question.
-
I don't think I've lost a lot, if any. I know Jobin was well ahead of me (seems like less now), and I'm sure Jamie was pretty close behind me (a lot closer than he is now!). @John Inder - depends on which one you get, but I've got two really good ones so far. Closest I can get to the more recent one is…
-
You need to get two things from the disk - the attachments, which Vasiliy already mentioned, which is a simple case of "copy a directory", and the database, which could be difficult. Problem with the database is that it varies between installs. "What database were you using?" is the first question, as it determines how to…
-
Duplicate of https://answers.atlassian.com/questions/39133934
-
For a quick and dirty one-off "put users in groups", I'd use Jelly. The tag http://confluence.atlassian.com/display/JIRA/Jelly+Tags#JellyTags-jiraAddUserToGroup should do it
-
All Atlassian trials work exactly the same as the full product - it's the same software. All that happens is trial licences expire, and your users see messages about trial licences in some places. If you decide to buy, you apply a full licence to the trial system and carry on working...
-
Right, that's simple then - you need to turn indexing on. Nothing else to look at here ;-)
-
Well, having data inconsistently displayed is very suggestive of an indexing problem. The trick here is understanding that the issue view screen is reading the database, but the reports, issue navigator and most other things read from the index. You should be able to fix that by running a full re-index. The question is how…
-
No, we don't need the whole log, just the errors - I very much doubt the one you've picked on is the only one. It's impossible to debug without the logs. But you can drop bits of the actual errors - we only really use the "ava.lang.NullPointerException at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:494) at…