Comments
-
See https://confluence.atlassian.com/servicedeskcloud/receiving-requests-by-email-747602718.html
-
Only project admins can create versions, so removing their rights to be project admins will do it. Otherwise, um, you don't want to, because they are admins.
-
Ok, that's ruled out everything I can think of, I think I'd want to raise it with Atlassian.
-
>While trying to delete in UI no errors appear Ok, what exactly happens - you click "remove" and get a blank screen? Returns to list of users? Returns to the user and shows them as still in the group?Are you in the same groups that you are trying to remove the user from too?
-
JIRA stops you from removing all the admins, you have to make sure that other people are in the admin groups before you'll be able to remove it. Could you tell us what group(s) you are working with, what the "global permissions" page says about those groups, and what the error message you get when trying to delete is?
-
Duplicate https://answers.atlassian.com/questions/287969/jira-web-site-plugin-to-allow-customers-to-enter-quick-jira-ticket
-
Long page loads and null pointers on saving are symptoms of something being wrong with the system, and you need to investigate that. Increasing the session timeout will not solve the problem - they could make it worse as more sessions will hang around waiting for data. It might help end users a bit, but you really need to…
-
drwxr-xr-x and owned by the user running JIRA.
-
A brief comment from the main technical author here - "It changes what I type in, so I can't debug it". I think they have a point here - the editor supports wiki markup as it's being entered, but then converts it into something that is not what the user put in, and is a lot harder to get "right" by tweaking later. I don't…
-
Yes.
-
Yes, workflow moves between status. I think you're asking how to prevent people editing an issue when it is in certain status? The default workflow does that on "closed" - you'll notice that although you can "reopen", you can't "edit" closed issues. The way to do that is with a property on the closed step. I can't remember…
-
Look for "workflow schemes" A workflow-scheme says "for issue type 1, use workflow X, for issue type 8, use workflow Y and by default, for all other issue types, use Z". The default workflow scheme says "use workflow X by default"
-
You need to separate out the "can log in" permission completely. You're nearly there by the sound of what you've said so far. Go into global permissions and look at what group or groups are given "jira user". The default is a group called "Jira users", but you may have changed that, so it's worth checking. Once you know…
-
Broadly, this has not changed. Although you do get a bit more notice as Cloud stuff is upgraded frequently and well before any releases.
-
No problem. There was one other thought I had, as I've done it with another system. If these "read only" users are not really going to be active JIRA users, you could drop them into another system. We set up a really simple scrape process - a shell script that * ran hourly * ran a filter over REST * took the resulting…
-
* Yes * Sort of * No JIRA lets people see issues based on their permissions and security. Permissions work at a project level, so at the most basic access is "a read only user is someone who has only 'browse project' permission". That lets them see all the issues in the project though. To protect indidivual issues, you can…
-
I can't replicate this as a bug - as long as my filter selects for a set of projects and issue types that story points are valid for, it works. I do think there's a massive flaw in the way Atlassian implement this though. There is some logic behind it, which does make sense when you work through it, but the fact is that it…
-
Have you raised this with Atlassian Support? Thanks for the warning of course, it could save some of us a lot of pain! Which version did you upgrade from though?
-
That's exactly the plugin I was about to point you at. I've tried installing it in Confluence 3.4.9 and it was not a happy bunny at all
-
Ok, I've just tried > -7d and that does what I expect - if the issue was resolved in the last 7 days, I can transition it. If it's older, I can't. Could you confirm that this is what "resolution date in beyond 7 days" means? Or is it something else?
-
Mmm, I think I have taken the wrong guess at what "resolution date in beyond 7 days" actually means (as written, it doesn't make sense). I think Ignacio's answer may be the right one.
-
I think your condition says "Block transition if the resolution date is before a week in the future", which will always block everything (unless you have a TARDIS handy) Try < -7d instead
-
I think this is related to https://answers.atlassian.com/questions/71438/can-i-select-multi-users-when-i-click-assign-button and probably answered (by accident) there as well.
-
There's not enough information to start to help you here. "Having problems" tells us nothing. What are you doing and what is going wrong?
-
No, there's no "assumption" about roles. Two things to look at. Start with the "permission scheme" for a project. Look at the line that says "browse project". A user will have access to your project if they match anything on that line. (It will probably say something like "all people in the role of users") Once you've seen…
-
I'm guessing you work with someone who has already had this answered today. See https://answers.atlassian.com/questions/9880868
-
If you make a field mandatory in Jira, it is mandatory for the whole lifecycle of the issue. To do what you want here, you make it optional, and add a "validator" to the resolve transition, which will stop the user completing the transition unles the issue has a fix version.
-
No, on both counts - space details are exposed because you allow access, and the space directory is there to allow users to list spaces that they have access to.
-
You'll need to read the log to find out what's going on. Jira won't make much noise when issues are created successfully, but it will tell you if it processes and drops incoming emails. Could be any reason though - sender not having create issue rights in the project is the usual one, although you might find that others…
-
This is not a 100% fix. Some fields will still show when hidden, if they had data before you hind them. You won't be able to add more data though, so of this doors happen, unhide them, kill the data, hide them again. Also, do NOT hide resolution. You need it unhodden and onscreen until you have edited your workflows to set…