Comments
-
Ah, that makes sense - it's very powerful, but with the post-functions, a lot of users don't grasp that they need to explicitly re-index when using it.
-
Ah, excellent! Interesting issue with the plugin - if you don't mind, could you tell us which one it was, so we can point other people at it if they run into it?
-
Yes, 5.1 improved it, so there's less need to explicitly re-index, but the symptoms you are seeing are very clear - it is not being done when it needs to be You need to isolate which post-function is causing the problem and work out why it's not re-indexing.
-
It's not a bug in the navigator - the navigator uses the index to read it's data from, whereas the issue view screen uses the database. What's happened is your index is not being updated, so it's drifted away from the database. The usual culprit is pretty much what you've guessed: * A post function is updating data after…
-
Jira doesn't support this off the shelf because * It's very counter intuitive - where I've done it, it's quickly led to complaints about the data being unrelated - users constantly saying "I've got X on my issue but I can't edit it" * It's very hard to define a generalised solution that will work for all customers The way…
-
Yup, it's not been added, you need add-ons to achieve it.
-
Does the person performing the transition have the right to set the assignee? What do your logs say?
-
The SQL you ran on it's own shouldn't have broken the project list. But if you had Jira up while it was done, it sounds like it has done something horrid and unpredictable :-(
-
I know it's not simple. Have you restarted your Jira and re-indexed it? You need to do that if you don't want to lose any data. Your SQL looks ok to me, but you really do need Jira offline and re-indexed to stand any chance of this working.
-
You could well have damaged your database, but, to try to rescue this case, restart Jira and then run a full re-index If you change data in a Jira database, then there are three basic rules * Backup the database first, as you could destroy it * NEVER do it while Jira is running, it caches stuff, and even if your SQL is…
-
RIght, so a different place to where you first said. That's ok, but you need to be consistent about it. could you now list out all the config files you have customised away from a standard installation?
-
Right. Could you tell us what jira.home is set to exactly in scenario 1? (I think there's something very broken in 1 which you're then copying over to 2)
-
I really don't understand what you've done then. For the home directory to become empty, you would have to botch JIRA_HOME, but this is being reported correctly, so it's not that. I don't know how you'd manage to clear it out like that. Could you go back and explain exactly what you have set up?
-
If you've relocated the directory to /local/caches, then the process needs full read/write access in there. I don't know what you mean by "setting/keeping the base directory"
-
It suggests that your indexing directory is not fully read/write enabled for the user running JIRA. Check the ownership and permissions of both the content of /local-jira and the contents of the home directory, including the symbolic link.
-
Yes, it would have been useful to tell us the full situation. I think this is a complex setup and you need to show us the conditions on this transition in full.
-
You don't even need script-runner for this - the condition "user is in group" is present in off-the-shelf JIRA.
-
They are separate subjects really. Your passwords for your users are one issue you've got. The mail server settings are nothing to do with the user account passwords. You need to set up an outgoing mailserver to send the mail from Jira on. The outgoing mail doesn't even need to be associated with a Jira account. There is…
-
The original question did not mention an application at all. There are several applications produced by Atlassian, one of which already does a "pick list" and "drop down" without any clever tricks. Confluence does not, so you'll need to find or write something to do it. But we can't tell you that without knowing which…
-
Um, you need to tell us which application you're looking at. (In Jira for example, it's a doddle - custom field of type "select list")
-
If you import Confluence, it will only wipe existing Confluence data - won't touch data in JIRA
-
Oh, that's new. And a bit of a downgrade IMHO, as you really should be able to simply bin a user for yourself. Thanks for letting us know, I'll have to scribble that down for next time!
-
Ah, I forgot... Adminstrative users automatically get "can log in" as well. Even if they're not in the users group, if they have system-admin rights, they count towards your licence overhead. (It does de-duplicate though - if "nic" is in confluence-users AND in confluence-administrators, I still only take up one seat). I…
-
Remove the deaded user from the group(s) that give them "can use" permission. You can see this in the Admin -> Global permissions section.
-
Depends on if you're running it with an affected Apache or something else that relies on bash.
-
Atlassian HTML macros sounds like the one.
-
Can't remember, but I know a ctrl-f search in the browser will find the addon with either Core, Html or Format
-
It's not an add-on in its own right, it's part of one of the core formatting add-ons. You'll need to open up the system add-ons and look for the modules that are disabled by default
-
The html macros are generally disabled as a security risk. Start by going to the list of plugins you have installed and find the one that provides the html macro. I suspect you'll find it is disabled - try enabling it. If that does not work, it should then give you an error telling you why it can't enable it.
-
Generally the same answer - quite likely that your JIRA can't talk to itself. Work through all the follow up questions (that people above have not bothered to respond to, hopefully because the question has lead them to see where the problem is, and hence fixed it)