Comments
-
Restrictions are for restricting individual pages. You need to look at the space *permissions* first, as they control access to the whole space.Space Admin -> Permissions is the tab you need.
-
It sounds like you've opened up the permissions too widely. Go to a space and look at the settings for permissions. What groups and users are listed? Check all three sections
-
There's a lot more information on the question this duplicates: https://answers.atlassian.com/questions/311261/get-filter-from-gadget-get-gadgets-from-dashboard
-
Deleting users will stomp on their history. Let's say I comment on an issue - if you then delete me, the comment becomes an orphan - instead of seeing my name and link to my profile in the author field, you will just see what my Jira user login id used to be before you deleted me. Same applies in the history of issues, and…
-
It's a bit of a fiddle on Cloud (in Server, I'd use the script runner to keep it more simple), but possible. You will need a different workflow for each issue priority you want to set. (e.g. if you have priorities of high, medium and low, you'll need three workflows). Obviously, you can get one workflow correct and then…
-
Ah, I see what you mean. Yes, that's the simplifiction aimed at the end-users - they don't really need to know the details of in-progress stuff. I'm not sure this is a particular improvement or a downgrade to be honest - it looks easier for users, but isn't as useful for those of us who need the details.
-
That sounds like a status that you've configured in your system, not a JIRA function, so I'm not sure how you were doing it in older versions - I can't see it in the version 6.4 or 7.1 JIRAs I'm looking at (they're obviously versions behind Cloud, but their release reports are very similar)
-
Thre's something wrong with the classpath you're passing into your Tomcat (also, check the version is compatible)
-
I think there's something in one of the Addons for Cloud/OnDemand that provides "copy custom field to assignee" as a post-function, but I'm not sure.
-
Well, the trick I've used is to create a new user-picker field that is not limited like assignee. Then when the transition or edit is committed, a script takes the user selected in there and tries to apply it to the assignee field.The weakness is that a user-picker lists everyone, not just the possible assignees.
-
No, this is a known problem - you can't assign issues to people who can't see them yet. So they need to be able to see the issue before they become the current assignee. In other words, using "current assignee" in security schemes is pretty much useless, and you can't do "user can only see issues assigned to them"
-
Not quite. You're right about permissions - they handle "who can see project". But you do need to use security schemes for this, because that allows you to hide issues inside projects. The reason it looks like a project thing at first is that you say "use this security scheme for this project" The way it works (over…
-
If you want Answers to stop emailing you reminders, it's easiest to mark the best answer as correct - look for the tick mark to the left of it
-
Ahh, I see, you've confused me by saying "time spent". Time spent by a user is NOT the same as "time in status". If I get assigned 5 issues, and I work on them sequentially, and all of them take 3 hours to deal with, I will spend 15 hours on them. The "time in status" will show 3h, 3h, 16h, 3h, 3h. Time in status is not…
-
Nope, no screenshot. Sorry.
-
I'm afraid Answers has quietly dropped your screenshot. However, I'm not sure what you're talking about now - time in source status and last execution date are nothing to do with the time tracking...
-
The time tracking stuff has been in Jira since at least version 3. If it's not showing any values, then you've not got any data in there. What are your users logging?
-
Add the timetracking fields to your issue navigator columns
-
Try adding the timetracking fields to your "status report" (I've no idea what you mean by status report - you haven't told us what you're running, but the issue navigator that handles searches allows you to select what fields you want)
-
Run a search for the issues in that status, save it as a filter and then use it in whatever reporting is most appropriate. I'm afraid we can't tell you any more than that based on your question - finding issues is pretty much a core function in Jira and you need to get to grips with it (as with a lot of stuff in Jira, the…
-
That is a good question - I can't find a definitive or obvious answer to it. Best I can do is point you to the new boards and try to say that you need to understand how they work and join up to your data before you will find the sprint display makes a lot of sense
-
For Q1:The purpose is to give you a view of how your project looks currently, from the point of view of someone working in an Agile way.It is not a "leftover", it's reporting the current stateThe reason you might be thinking that it is "wrong" or "not useful", is because you need to understand how the data you ask about in…
-
Jira does not do field level security. See https://jira.atlassian.com/browse/jra-1330 for the standard set of workarounds and discussions. (Plus https://marketplace.atlassian.com/23216 of course)
-
I don't know of anything in Confluence that would do that, even given your partial uploads. (by the way, 500Mb files are not something Confluence is for really, it's know not to handle large files brilliantly, and that's why the default limit is 10Mb. For large files, you probably need some other file store system and…
-
That is not something confluence would do. One of your admins, or a Windows process has moved and renamed it, and Confluence is simply telling you it's not there any more - it's been removed by something outside confluence.
-
The security needs to be set by the creator - make sure the security level field is on-screen and they have the "set security level" permission. A lot of places also skip that and do it with a post-function, which can confuse the user if they don't have "view" rights after the security is set, but makes sure they get it…
-
Could you show us the header of the issue-type-screen-scheme?
-
Could you check that you have created an "issue type screen scheme" and not just a "screen scheme"? The "issue type screen scheme" should be listed when you use project admin and try to select a new one, and they contain one or more "screen schemes". It's a common mistake for admins to mix up those two things, create a…
-
Use "duedate < now()" as part of the JQL query you are building.
-
Hmm, I don't know. It would make sense if you could do anonymous read, like you can here (which is Questions), so I'm pretty sure it's possible.