Comments
-
Mmm, Jira security is powerful, and hence complex, and I think you've gone in the wrong direction! First, security schemes are there to protect individual issues within a more widely published project (example - a project for logging incidents is available to all users, but in cases where the fault was human and the…
-
Setting a field to a value is easy if you have the script-runner addon (or you can write your own functions to provide it). You can bring in "value depends on reporter" there as well. However. JIRA does not do field level security. You can't make a field read-only for some users and read/write for others, without either…
-
Ah, no, you have probably not "permanently fixed it" - you don't know what the *cause* of the broken index was. Because you don't know the cause, you haven't changed anything to fix it, so you could easily end up with more broken issues. You may not see it again, it may have been a one-off cause. But you don't know that.
-
I would have typed something saying the same myself, but I'd emphasise the point that there may be a more serious underlying problem. Indices that don't match the database strongly suggest a structural problem. The usual suspects are server interruptions (accidental reboot, power loss, forced kill of JIRA), bad code in…
-
Not for Cloud. For server, there's a number of varying ones - just try "rate" or "vote", or "survey" in the marketplace.
-
No, an issue should only appear on a board once, so it will land in the first swimlane it matches and not be repeated.
-
I'm afraid not any easy ones. At a glance, Jaime's SQL should have worked, if you do it on a shut-down JIRA, so that may be worth a look. (Sorry, my original answer should have included "an active jira database"). But as it's not done anything at all, that suggests that there is an issue with it.The other trick might be to…
-
I'd still avoid it - you've already discovered that it's not working.I think it should work in theory, but I'd also say you absolutely have to have the system offline. There's only one minor thing I would change with SQL in a running JIRA (and I don't need to since 6.1)
-
That is NOT JQL. JQL is for searching for issues. You are running SQL, which you should NEVER use on a JIRA database. I'd strongly recommend undoing the damage you've done and restarting again.
-
Ok, the plugin is installed and fully licenced for premium use? It should tell you that when you expand the entry in the list of addons you've installed.What do you get in the macro browser when you select "all" and then type AUI into the search?
-
Which "format macro"?
-
It's the view stuff documented at https://confluence.atlassian.com/display/GH/Using+the+Task+Board but you also need to check that your visible columns include the "new" issues
-
I think you need to look very carefully at the filter settings in the task board - check the "view" settings. It may be that your task board is set to (say) "show me issues in version X, and filter it through 'assigned to me'", so if you create a new issue that is not in version X OR is not assigned to you, it won't appear.
-
That sounds very odd, and I can't replicate it on Cloud. I think it needs to go to Atlassian support for more investigation - https://support.atlassian.com
-
Could you explain the symptoms you are seeing? Also, test it with another browser, does that do the same?
-
Performance - not really. Obviously, any database service can become overloaded, but there's nothing unusal about running several Atlassian apps in databases scattered across services or in one place. Upgrading - not an issue - the sets of data are separate, so the upgrades are independent. Other advantages - that's where…
-
Yes, it's perfectly safe and has only one minor downside - if you need to take the database offline for maintenance, all the applications suffer downtime.
-
It's a really bad idea to try to do this. The JIRA database is NOT suitable for reporting or anything other than being a datastore for a JIRA server. It's complex and messy, organically evolved, and you're going to need to find and maintain a hideous data dictionary for it. There is a data diagram available of course, but…
-
If the field doesn't have any decimal places, that implies you've changed your JIRA look and feel to hide it. It's still a numeric field though, and that's how Confluence reads numeric fields.
-
It looks like a JIRA macro for filter results to me, but even if it is, the principle is the same - it's a faithful representation of the data the macro is reporting on.
-
Try the "content by label" macro. (I am guessing you mean Confluence, as you've not said)
-
There are some options for exports. What are you looking for?
-
Ah, ok, you hadn't mentioned fields before. This makes sense.Jira does not do field level security. See https://jira.atlassian.com/browse/JRA-1330 for the discussion, workarounds and reasons Atlassian won't be doing it.Although to save you some reading, the answers are broadly:- writing fields that can do it- botching it…
-
Sorry, you've effectively said "user's project role belongs to role". It always does, they're the same thing. Could you explain what you're looking for? I don't understand what you're asking for here.
-
Yes, you'll need a listener to catch the edits of fixversion, unless you remove it from the general "edit issue" screen. (Also, you'll need a listener if you have greenhoppper).
-
Inside Confluence, annoyingly, no, the option to relocate attachments was removed many versions back. There are workarounds at an OS level though. If you're using a Unix-like type of operating system, you have two dead easy options - mount the NAS as a directory somewhere, then either replace the attachments directory with…
-
No, that doesn't work, if you mean "you can blank it out". You still have to set it to something if you use a post-function, because:- It will still appear in lots of places- You'll have to fill it in if you want to edit or transition an issue- Lots of places (especially add-ons) break in interesting ways if it's empty
-
You can't. End of story. The closest I can get if I'm allowed to code is to have a Summary that you fill with something by default on the create screen, and overwrite it with your own string in a post-function if you want (strongly recommended, as it's going to appear in lots of places no matter what you try to do to hide…
-
Not ideal, we fixed the first case by letting the chap lose his password and taking a week to reset it, then gently pointing out that if we hadn't killed off his email, he could have reset it himself in seconds.
-
A user who wanted no notifications ever.Dummy users for automated operations which would generate emails that would be ignored.