Comments
-
I'd use a scripted field to expose it, but it could get very complex as status doesn't necessarily map directly on to columns (a column could contain more than one status, so you're into adding up time in several status then, and it won't be easy to do on the fly either) The closest you've got is the dots for "time in…
-
Ok, these are different things, despite the name. * The "time in status" field is a non-human-readable data store for some information used in the charting add-on. Don't bother putting it on screens (or cards), as it won't do anything useful * The "time in source status" thing you see on the transitions tab is not a field,…
-
Both. Don't add it to most screens because the content is not really human readable. Don't put it on a transition screen because it's also going to be wrong, as you're part way through something that changes the value.
-
Ah, ok, the question (before it was edited) did not mention the import tool or JIRA. The process of import has nothing to do with Pivotal other than copying the information into JIRA. It won't change it in any way.
-
You might want to ask that in a Pivotal forum, this is a place for Atlassian users.
-
1. Yes, enable the "modify reporter" permission for your internal users, and make sure the field is on the "create" screen. However, you do need to have an account for each user (you could make these dummy accounts - cannot log in, and hence will not use a licence. They'll have to rely on anonymous access to see your…
-
Yes, it's blasphemous, but sadly very valid. If the heretics don't ask, they silently go elsewhere. If they do ask, at least there's a chance to convert them back. (And I speak as a heretic - I'm really struggling without wiki markup - it's simply not working for me)
-
I can't see from that which transition is "missing", because we can't see the current status, whether you have "can transition issues" permission in that project, or what the conditions on the transition are. In the flow diagram, could you tell us which arrow is missing, then what conditions are on it. (And check your…
-
Ah, that is exactly it - your condition is an AND, and you probably want OR. Well spotted Rambanam
-
I don't quite understand where the problem is. You have added conditions that say "current assignee" and "reporter" can perform the transition, and it's not letting other people do it. That sounds right to me. Could you check what the assignee is seeing - the screenshot you gave is only really part of what we need to see -…
-
No, the condition "assignee" means the current assignee. The person currently named in the assignee field. You don't really say quite what you're trying to achieve here - if the sentence above doesn't help you enough, could you explain what you are aiming for.
-
Sounds like the current user doesn't have all the required access - specifically, this is exactly what happens if the creator does not have the permission "assignable user". If they do not, then they cannot be assigned the issue and Jira is reverting to the rules for automatic user. Check the permission scheme again.
-
Yup, it's a common acronym in computing. But we'll need a bit more information to help you with your question about it. (At a random guess, yes, you can "integrate" JIRA with CMDB systems, and I've even set it up as a basic CMDB in itself)
-
It's not there because it's an unbounded value, and the gadget requires countable values. The nature of the time spent field is that for 1,000 issues you have 1,000 separate values. Some of them might be the same. All of them might be the same or limited to only a handful of values, but there is still the option to have…
-
I'm unclear on the upgrade comment - are you upgrading this installation or not? This has just started happening? Is there a chance you've accidentally pointed the upgrade you are doing at the database behind production? On the rest - select lists, 4.1.2, good, and it's helpful that it's existing issues and new ones are…
-
Have you upgraded recently? What type of fields are the custom fields? What does your log file say? What version of Jira are you running?
-
That's the same question you asked earlier. See https://answers.atlassian.com/questions/45953987
-
Hmm, yes, it should really have "from the issue action menu" added to the sentence.
-
"When they're ready". That's the Atlassian line. From assorted mailing lists, blogs and so-on, there's something on the way for summer 2013 - looks like a framework that will give you more flexibility to add plugins into OnDemand, but I've not seen a lot of detail, or scope.
-
Components and versions are maintained by the project administrators. They can be found under the project summary screens (e.g. for project XYZ, start at http://your-jira/browse/XYZ)
-
You don't. You don't need different screens per step, as when you look at an issue, you use the "view" screen - the status is irrelevant. If you click edit, the status is also unimportant, so you just have the "edit" screen. Moving between status is a different story, this is where you often do want a different screen. To…
-
This is probably something you need to take up with the author of the Jenkins addon. I'm not aware of any updates to it that would make it work over REST instead of SOAP, so I'd check with them if they're going to do the required changes.
-
Version and status are very different things - there's a whole workflow engine behind status. Anyway, no, there's no way to drag epics into versions, I'm afraid you have to do it in the issue view, by editing the epic and simply adding the version. Although, the Canvas add-on should be able to do this, I think.
-
I'm afraid the question is unclear on what you're trying to do. You can set a version on an Epic if the version field is on Epics, but I'm not sure what the rest of it might be.
-
That's the same screen shot. Still no tooltip.
-
You will need to edit the .css that specifies the colours in the menus. I'm not seeing a "tooltip" in your screenshot though, so I'm not sure exactly what you're talking about.
-
What are you trying to "synchronise"? There's no information here. The error does lead me to think that whatever process you are trying here, it doesn't have the permission to change the priority on the issues, but it's hard to know Could you explain what you are doing that throws this error up?
-
No, you can't do that without code or an add-on.
-
* See https://confluence.atlassian.com/display/JIRAKB/Disable+relative+dates+in+JIRA+applications * You've got a time zone problem on the server (probably). You can test this by forcing the correct timezone for the java virtual machine in the setenv.sh/setenv.bat file (from memory, -Duser.timezone= )
-
First question * Change the name of the fields - just add a . to the display name or something clear like that. * Run a filter for each one (e.g. "Epic Link is not empty", "Epic.Link is not empty", "Epic..Link is not empty" ). You can kill off any that return 0 results. * Where you have results in more than one, you'll…