Adding comments to issue for SMTP errors

[Johannes]

Hello,

I have the following situation:
My users are sending out mails (with Add-on "Email this Issue") and sometimes the sending fails because of some SMTP error (e.g. attachment size too large etc.) thrown by the mail server.

These errors are however only visible in the log files, but not for the user who sent out the mail.

Is it somehow possible to show such error messages to the user, for example by adding a comment to the ticket from which it was sent?

Thank you

Johannes

[Deleted user]

To correct C. Faysal:

1. Figure out what property ID represents the license key. For new versions of jira it will be:

   select id from propertyentry where property_key = 'License20';

2. Now you can update the property, just replace the placeholders:

   update propertytext set propertyvalue = #{license_key} where id = #{jira_license_prop_id};

[Administrator]

Thank you! This helped me so much when my JIRA didn't want to run after an upgrade to 6.2.1 :-)

[Nic Brough -Adaptavist-]

I've not seen Jira install the licence as a file. But you can poke it into the database.

(Sadly I can't remember where, it's been a while since I scripted it into a failover system - I'm pretty sure it's one of the propertyentry rows, but I'm not certain)

[adam valenzuela]

The only way I have been able to achieve this is by doing the entire install one time, say on a test box (including clicking around the wui) to obtain the fully formed response.varfile and to populate all of the needed XML files. Then I just wrote a bash script which performs the very same install using that "response.varfile" along with a copy the "dbconfig.xml" which was previously created.

Perform install w/response.varfile

Stop jira

Copy over dbconfig.xml to "jira data" directory

Verify permissions

Restart jira.

$!BOOM

With that that formula I am able to kickstart a fully usable jira box without touching the keyboard. I will note that this method "may" cause issues with licensing down the road, but if you are in a heavy dev-env which may involve flipping these installs like hotcakes then this might work for you.

Still working on combing this w/ the ~/bin/config.sh to setup https out the gate.

[C_ Faysal]

As nic said you can inject the license by sql statement. I need to be on a non-mobile device to view my backup script where i did exactly the same. I will post the cmd asap

[C_ Faysal]

here you go:

update propertytext set propertyvalue = '$jira_license' where ID = '10021'"