In one of our Jira projects no one is able to edit the assignee of an issue (except the current Assignee and the Reporter of the issue)
I know that there was something set up, that the ticket is not editable for people who are not assigned to the ticket or the reporter of the ticket. But this should not relate to the assignee field, but more for all other fields.
Do you maybe know where I can change that? I've looked up the permission scheme, but there it should all be set in the right way. Any other ideas where I can have a look?
Thanks
I solved it myself.... it's a BIT of a hack but I created a service account in Jira with the correct name and email address but doesn't have log in privileges. Allows it to be used as the reply to but doesn't take up a license.
Seems a recent update of JMWE allows one to spec the system email address as the sender... I've coded around it (and actually turned out to be a better solution) but resolved now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Another option is if you also have ScriptRunner installed, it also offers an email post function, and in its configuration section you have complete control over to, from, reply-to, cc, and bcc addresses (you basically have an instance of an Email object [https://docs.atlassian.com/atlassian-mail/1.3.23/com/atlassian/mail/Email.html] to do with as you please).
-Payne
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Payne. I did look at that and keeping it in my back pocket if I can't work out the rabbit hole I am down right now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately, Jira decides on its own what the Sender information should be - the Ad Hoc Notification API just allows to specify the user that should be considered as the sender, not the reply-to address.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @David Fischer
As mentioned I found a work around but I am also going down another direction by putting an html tag in there with the response I am after (actually solves a few problems by doing that)
What I am doing is having users NOT in JIRA be able to transition an issue via email (keywords with Automation transitioning when it sees them). The "instructional" email coming from a PF. I'm now creating the html tag to create the email automatically with correct reply-to, subject line, and key words in the body. Serves to drool-proof it a bit more.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.