Comments
-
That's answered it - you've got "any logged in user" in the permissions. Change that to a role of "user" instead.
-
Could you show us the permission scheme you're using. I asked specifically for the "browse" line in it.
-
Have you removed the standard groups from the roles? The defaults are to put jira-users into every project "users" role, which allows them in. As jira-users is also the group of "can log in", it grants access to everyone. To confirm this with our help, could you show us what you have for "browse project" in your default…
-
No, although it wouldn't be hard to write one. However, I wouldn't recommend it - JIRA is an issue tracker, not a system monitor. You should really be monitoring servers with software designed for that purpose (although when you get disk alerts, you can log them in JIRA). If you implement something for disk space, you'll…
-
Oh, the Behaviours addon, I didn't make the connection. I'm not sure it handles inline edit that way yet.
-
You can't define a field as read-only in Jira unless it's a genuine read-only field (can only be set by code) or a field you do not put on Create, Edit or Transition.
-
This is the "inline edit" function that lets you quickly change fields without having to leave the view screen. The function respects the settings in your "edit" screen, so if you remove fields from edit, they will no longer be editable in view. There's a request to be able to partially or totally disable inline edit if…
-
No, an account represents a single user.
-
No, that's not what happens. Individuals log time with their name on it. Doesn't matter who the assignee is or how it progresses through the workflow. A work log remains logged by the person who did the work. It's nonsense to do it any other way - timesheets wouldn't stand a chance for a start. Where are you getting the…
-
They are moving towards increasing flexibility in Cloud. But in my opinion, they're not ready for the current focus on Cloud. Cloud Connect doesn't have the extension points we need for the really powerful add-ons that many customers need and they need data-centres in the EU before EU users can take it seriously. There's…
-
Bascially, no. (Barring the fourth one - you move "issue field edits" into the workflow and control access with conditions) Kepler add-ons and the Script Runner are never going to be available on Cloud - Atlassian are not adding more "type 2" add-ons, it's Connect add-ons only, and they don't yet support the flexibility…
-
A field's "mandatory" flag is independent of screens, it's got nothing to do with them. Jira is behaving correctly here - you might not have the field on screen, but you've told Jira that it should be mandatory, so Jira is demanding that you fill it in. You'll need to either make the field optional and use validators in…
-
There's an add-on that provides a lot of audit functions for most versions of Jira. But a lot of it's functionality is being absorbed into Jira 6.2 and above. If you've got 6.2, go to admin and search for audit. If you've got 6.1 or below, have a look in the marketplace for plugenta
-
I have some ideas around the fuzziness around using "in" on text, but a bit more testing might be useful. Let's say two of the common words your users have put in this field are "Cat" and "Penguin". Could you tell us what you get for: project = "MyProj" and "Cat" NOT in (MyKey) project = "MyProj" and "Penguin" NOT in…
-
Three things I'd look at: 1. Your spikes of activity are mostly suspiciously evenly spaced. I'd do a bit more monitoring and see if the spikes are forming patterns of usage. Like 11:20am Mon-Fri. 2. You say "the amount of data logged to the file is so insane (20MB each 3-4 minutes) that it is simply impossible to find any…
-
So frequently, it's not really given a simple fixed date. Have a look at https://www.atlassian.com/university/training?tab=jira-software
-
Ok, that makes sense. >whenever some confluence user creates his personal space, our own build theme or layout or template should be used in building that personal space so that all personal spaces should remain constant (similar page content and style). That's exactly what themes are for, if I've understood correctly.…
-
I don't think you've grasped what you're asking here. The $body contains the *body* of the page that Confluence is going to draw for the user. You don't mess with that in a theme because whatever you do will affect every page using that theme, and the $body is quite simply "what the users have put on the page". Themes are…
-
No. Jira doesn't do field-level security. Your only option for OnDemand is to move the field into the workflow - remove it from the "edit" screen (and maybe "create"?). Create a new screen and put it on that, then use that screen in new transitions, and put conditions on those transitions to say "only person X" can use…
-
Um, if you can't see your profile, how do you know the email is correct? If it really is correct, and the reset doesn't work, then there really is no choice other than to find your administrators. I'm afraid there is nothing we can really do here - your admins are the only ones who can help you here.
-
There's a "forgot password" link under the login box usually. If not, then you probably need to contact your admins.
-
Internally, no, nothing specific. But you could set up a trigger to poke something into a remote service. Although the most simple solution would be to use the standard event/notification to send email to a dummy account which could parse the content and relay it to your SMS provider. (Guess who's done that before...)
-
Not that I know of. All the stuff I've worked with was only reliable or useful if you took the 6.1.4 and upgraded it to 6.4.11 then did export/import
-
You've answered your own question! >My question is how can I migrate projects without doing the upgrading step? >I know that first I have to upgrade the version of the old one to the same version of JIRA destination. Database work in JIRA is often ugly, and usually leads to all sorts of "interesting" breaks and recovery…
-
You don't need JQL functions to search scripted fields, they appear as normal fields as long as you've got a searcher for them.
-
Scripted field values are not held in the database. You can search for them with REST or the UI as though they're standard fields though.
-
Two things 1. It's a lot of work to decide whether a field should really be there based on all the possible combinations, then you have to decide what to do if the field visibility is changed - e.g. if you remove field X from a screen, do you automatically remove it from the Agile view? What if there's a mistake and you…
-
You don't. An issue is either done, or you're still working on it. Kanban is not really that focussed on distinct and discrete release packaging. The giveaway in your question here is you've mentioned "sprint". If you're doing Sprints, you're not doing Kanban. I suspect your only option is to release as per Scrum or…
-
Why do you think you need the old licence?
-
You can find it in your my.atlassian.com account.