Comments
-
Yes, you can.
-
No. If a user can log in, then they consume a licence. What you can do is allow anonymous access by adding the "group" called "anyone" to "browse project" permission in the permission scheme for projects you want to make public. One word of caution - never grant this for anything other than browse project permission, as…
-
It might be the Behaviours part of Script Runner, but you'd have to have done some sneaky stuff with it, and you should be able to see that in the admin section. I assume that your users can assign issues with the "assign/assign to me" links (if they can't, then Fabio has given you the right answer) But... the usual reason…
-
Yes. That is right.
-
Sounds like you are not quite getting how the schemes work. * You need a workflow for bugs * You need a workflow for requirements * You need ONE workflow scheme to tie them together in a project (the scheme says "use workflow x for issuetype 1, y for 2, z for 3" etc) * When you change a project from one scheme to another,…
-
There's two parts to this * If you want unassigned issues in some places and not others, that's possible - in the project/issuetypes you want the assignee to be filled at all times, use the field configuration to make the assignee mandatory * JIRA doesn't support this in the "automatic" options (you can do unassigned,…
-
I'm really sorry it took so long to get to something resembling an answer!
-
Administration rights are not the same as project rights. Can you explicitly check that this user sees the reporter field and can change it when manually creating an issue? Also, can you try regenerating the issue collector javascript and check that it's the same in the application you're adding it to?
-
Sorry, I realise that was written totally incorrectly. Rather than edit my post and confuse the thread, I'll try it again The issue collector does not require anonymous access. I wanted to check how that worked, and that looks fine to me. The next test I had in mind was to log into the UI as the person you have set as the…
-
Well, that's the answer then. The collector has to respect the permissions and security in Jira. You've told Jira "no anonymous creation of issues", so the collector can't do it either.
-
Good, but what abou the last test? What do you get if you raise an issue in the UI while you are not logged in?
-
Start by trying to create an issue in Jira's UI first - do you get all the fields you need in there? Then log out and try the same anonymously - still all the right fields?
-
Ah, I wasn't far off then! Sorry I missed "make sure field is on screen" though. I didn't thnk of that.
-
I wouldn't worry about issue types, I think it's the reporter field. You've got anonymous-create and optional reporter, but there's a third permission for "change reporter" in the permission scheme. I suspect you need to allow that to "anonymous" as well as "create"
-
I'm afraid you can't - the : is used by Confluence to separate Space:Pagename so, although you can use it in a page name, it can't be referred to by the internal linking system.
-
What validators and post-functions do you have on the "Verify" transition? What does your log file say at the time you click the button?
-
I do think you need support to take a look at the logs. If you can send a test email and it arrives, then the underlying "get mail from A to B" is working. If your notification scheme says "on Event A, mail user B", then Jira is definitely trying to send the mail. Anything in between those two needs a sysad to check logs…
-
I would 1. Check that your notification scheme has not been changed 2. I don't know if you have the "mail server -> send test email" option in OnDemand. If you do, then try it, and enable the smtp logging. If you don't, then ignore me and move on to 3... 3. Raise it with Atlassian OnDemand support. State that you've…
-
I think we moved past that point, but you do put it very well. Problem though - it's not a design flaw - A in context 1 is not the same as A in context 2. They're separate items that just happen to have the same name.
-
We need to see a screenshot of the custom field section that includes the field you're struggling with and to know the issue type. None of the text stuff though - I imagine knowing that vendor "dave" is "restricted" might be sensitive, but if you don't show us "dave", just the classification field, it should be ok.
-
Look at the plain issue view you get from https://yourjira/browse/ABC-123
-
I meant the custom field section - the fields and their contents.
-
And does each click give exactly the same list of issues? If so, could you pick one of those issues and show us the custom field section?
-
Hmm, ok, so when you click on each of the two "restricted" links on the pie chart, do you get the same set of results each time?
-
Possibly. Is, "restricted" available in more than one of the contexts?
-
Sorry, by context, I was looking for the field context, not the option list. Is it a global field, or does it have assorted contexts?
-
Could you tell us about the statistic you are selecting? What type of field is it, and what contexts does it have?
-
You'll need to show us the exact config for the field and the results from filterst hat summarise what eh pie chart might be trying to show you.
-
Ok, and what is the statistic type?
-
I assume the pie chart is reporting on the custom field? Do you have two entries for "yes"?