Comments
-
You can't. You might raise a support call with Atlassian to see if they might set the flag for you, but as it's a restricted function, they could easily say no.
-
See https://confluence.atlassian.com/jirakb/disable-relative-dates-in-jira-applications-414187622.html - bear in mind it is a global setting, and you can only do it on Server.
-
You do it in your my.atlassian account.
-
Make sure you have * The global permission for bulk edit * The project permission for delete issues Then search for the issues and use the bulk-edit option in the tools menu to delete them en-masse Be warned that delete means delete - there's no getting them back.
-
Try finding them via the groups or roles the incorrect account is in.
-
We can no longer turn off the new experience. Please go vote on the issues raised in JAC - comments here don't get counted.
-
Because Jira has simple initial templates for certain common types of project. If you want an issue type of "risk", that's great (and I'd applaud you for thinking of doing it in Jira too - it's a good move). You'll need to add a risk issue type as an admin, and then add it to your project's issue type scheme.
-
That's fine, we can still work with it. On the first one, you have an estimate of 1d. Then someone edited the issue and adjusted the remaining time, rather than log work. In the second, I would guess that the 30m logged has been knocked off, but that someone has also altered the remaining time by 2 hours as well. In both…
-
Why? If they know enough to turn off javascript, then they should know enough about the usual problems it causes, well enough to recognise when they should re-enable it.
-
My best guess is that you've landed here by mistake - this is a place for people to talk about Atlassian products. As it happens though, I've been working with Artifactory and Bitbucket today, so https://www.jfrog.com/confluence/display/RTF/Installing+Artifactory was close to hand.
-
That does not show your 9h as 2d anywhere. Neither of those pictures are related to the question and there's nothing to show that they might be reporting anything incorrectly. I am confused now.
-
That is the point - you should not be estimating on sub-tasks. Burndown is supposed to be done on stories, when the whole item is delivered, not bits of it That's part of the reason Atlassian have never implemented anything for sub-tasks.
-
Yes, it relies on javascript. You need to enable it.
-
That doesn't look right to me, as that 9h should be 1d 1h. Where exactly are you seeing the 2d for 9h?
-
Hmm. I suspect you have already turned the "pretty" off. If you were using pretty time, you should see 9h shown as 1d 1h, for an 8 hour day. I suspect you've turned that off, and set the display to "days", which means Jira will show anything under 8h as 1d, 8-16 hours as 2d, 16-24 as 3d and so-on. Go back to the time…
-
The admin can set a name when a new account is created, because it's new. The reason you can't change it later is because it does not belong to the organisation. I don't think you're actually disagreeing with my statements (they're not opinions, they are statements of how it works and why you cannot allow admins to edit…
-
Because you commit to doing stories in a sprint, and a story is either complete in the sprint or not (and if it's complete, then you burn down). You don't commit to doing a story and then say "well we got halfway through it" at the end of the sprint. It's either done or not. What scripting add-on do you have?
-
Could you explain what this has to do with Confluence?
-
Jira "prettifies" the numbers into larger time units when it can. If you're getting 2d when entering 9h, then it suggests you have set your time-tracking to treat a day as 4.5 hours
-
Ah, I see. Do the opposite then. Run "And fixVersion not in (v1, v2, v3, v4, v5)"
-
>I don't think any admin should be able to edit your identity So you see why you cannot edit the full name of someone else's account now? The analogy with the passport still stands even if you don't have a full name on it. It's still my identity and there's no way another country should be editing any of the details on it.…
-
I think Michael has got it now. But the point still stands - while you're inviting me into your system, that's great, but why should that let you edit my identity? Should everyone who invites me in be able to edit it? Compare it with a passport - it lets me into other countries (when invited), but the country I am visiting…
-
It makes perfect sense when you read the previous comment.
-
First, get a proper description of what you want from "integrate", then you'll know what to look for in add-ons and where you might want to set up data flows between the two.
-
Remember that it will default to the last one you used as well.
-
It wouldn't have been that that fixed the search.
-
It looks like the user directory may have gone wrong. What was it before the update? Internal or external?
-
Er, that's nothing to do with a search not working.
-
Yes, re-arrange them in the issue type scheme for the project.
-
Imports, merges, reporting, automation, housekeeping, and lots of other stuff clients sometimes ask for. I do it all inside Jira with ScriptRunner most of the time.