I restore the DB form JIRA B to JIRA A by SQL server.
Then I want to set the JIRA A's outgoing mail to disable automaticly.
I think this setting was store in the DB. So how to set Outgoing Mail DISABLED by edit DB?
Thanks very much!
It is strongly recommended that you do NOT change the database in JIRA. It's not as simple as people seem to think it is.
Use the command line flags to start JIRA A instead - see https://confluence.atlassian.com/jira/setting-properties-and-options-on-startup-120007.html ( i.e. -Datlassian.mail.senddisabled -Datlassian.mail.fetchdisabled -Datlassian.mail.popdisabled )
Hi xinan, as Nic said, it is recommended not to change values directly in JIRA database.
Anyway, if you really need to do it this way, you'll need to execute the following query and restart your JIRA instance:
UPDATE propertynumber SET propertyvalue=1 WHERE ID=(SELECT ID FROM propertyentry WHERE ENTITY_NAME='jira.properties' AND ENTITY_ID=1 AND PROPERTY_KEY='jira.mail.send.disabled');
Regards
These options are already present but commented out in in the setenv.sh and setenv.bat that ship with JIRA. I would simply uncomment them rather than trying to do anything fancy. In setenv.bat: rem -------------------------------------------------------------------------- rem Uncomment this setting if you want to import data without notifications rem rem -------------------------------------------------------------------------- rem set DISABLE_NOTIFICATIONS= -Datlassian.mail.senddisabled=true -Datlassian.mail.fetchdisabled=true -Datlassian.mail.popdisabled=true In setenv.sh: # Uncomment this setting if you want to import data without notifications # #DISABLE_NOTIFICATIONS=" -Datlassian.mail.senddisabled=true -Datlassian.mail.fetchdisabled=true -Datlassian.mail.popdisabled=true"
@Nic Brough -Adaptavist- ,
Could you please tell me how to uncomment the lines in the setenv.bat file.
Remove the "this is a comment" indicator character(s) from the beginning of each line you want to enable.
Looks pretty simple to me. Pretty basic sub-select. If he's like me, he's doing it in a test or development environment prior to Jira startup, so what's the risk?
With this particular database hack there are two main risks
1. It probably won't work. It certainly won't work without restarting, and if you're doing that, you might as well do it the supported way, as it's quicker, safer and more reliable.
2. It encourages people to do things in the database. Which is a very very bad thing.
It looks like you're new here. Sign in or register to get started.
