We have custom user fields (ie 'Business Analyst', 'Developer', etc.) in JIRA, and we would like to be able to send an email to those users when they are assigned to one of those fields. I have looked over the JIRA wiki, and could not find a way to do this.
I know this is possible with the 'Issue Assigned' event, but in this case, the JIRA is not being assigned, since we are using custom fields.
Is this at all possible?
This plugin: Email This Issue should be what you are looking for (sending email to custom fields).
Email an issue from JIRA to arbitrary recipients - This plugin
addresses this feature request fulfilling considerable amount
(currently 30) of user votes.
The plugin contains an issue operation component that allows users to
compose an email and send the issue to arbitrary recipients.
Most important features are:
send email with issue details to email addresses outside
JIRA,
assignee, reporter and watchers. attach issue attachments to email control who can invoke the operation
through a project role text and html email format are
supported, email body understands
Confluence wiki markup email template can be customized per project and issue type a comment is created
reflecting the event of sending an email
(body, recipients, etc) - see below i18n-enabled, the plugin can be translated, it is currently
available in English, German, French, Polish, Italian and Hungarian. you have options like "CC to me"
and "Reply to
me" to receive a copy of the email or to receive replies to
the email. < li>email recipients are added to watchers on demand recipients from custom fields and
groups/project roles can be added email options may be
reused, i.e. there is no need to check all
your options every time you send an email configure default values for email options via configuration file
You should look at the JIRA Scripting Suite plugin --- you can easily do something like that, and in fact, they provide a sample script that shows you how to send a custom email (https://studio.plugins.atlassian.com/wiki/display/JSS/Scripting+Samples).
But you do have to catch two use cases --- as a post-function to a workflow transition and as a plain edit. This plugin allows you to do both of those. I typically just worry about handling those things at the point in the workflow in which those fields are required for the first time, and handle it in a post-function.
This plugin completely changed the power of JIRA for me. I can quickly change scripts on the fly without recompiling or restarting JIRA. You must check it out.
Related
I'm using telegram bot and can get user id from incoming message.
Sometimes I want to find users who communicate with telegram bot and write them message by myself.
I have only user id and have not some additional information about the user.
Can I somehow find users by id or anonimity with only id available is by design?
At least what I've been using...
Program your bot to send you a message with link to that user.
This can be done by using link in your message (must be used as message entity or inline keyboard button):
tg://user?id=<user_id>
Or in case you are using MarkdownV2 for formatting
[inline mention of a user](tg://user?id=<user_id>)
Then, by clicking on that link, you will open a user profile, where you can message your target.
Note, user can change his privacy settings, and disable mentions. In this case these links will not work.
I have question about registration process in selenium. Which way is best to do it if we must click activation link in received email? Which method is used by commercial QA teams?
I am thinking about this problem and I want to use sites like '10 minutes mail', is that a good way?
There's any other options? I can't use same mail multiple times.
Creating new 'true' mail every time will be difficult and will take too much time, there will be captcha problems etc
you can use a mailbox as registration mail, which supply API to read mail content in inbox, rather than only can from UI. Therefore you can easier to get the activation link and send http request to simulate click activation link.
Try using regular gmail account, there is a trick with '+' character and You can re-use multiple times, and mail is getting received on same account.
So You can use like this: open gmail with desired address, eg. address testmail#gmail.com, so You can reuse it in following iterations:
testmail+1#gmail.com
testmail+2#gmail.com
...
testmail+test1#gmail.com
testmail+test2#gmail.com
and so You can have...lot of accounts. I've used this method and its quite sufficient.
I am using AWS Cognito to verif users' emails by sending verification links to users' email. After users click the links, a default confirm message "Your registration has been confirmed!" is shown. Is there a way to customize this message?
Thank you!
Currently (late June 2018) this still appears to be not supported. It is a pain because users should be redirected to the app in question after confirming their account, but currently they must navigate themselves.
There is a proposed workaround (essentially customizing the confirmation e-mail to send the user to your own API that performs the confirmation in a lambda), but I have not tried it. There does appear to be demand for this and AWS is aware of it as a feature request. I've seen them adding more customization abilities to the Cognito console recently, so keep checking there for updates.
If you're using the Cognito-hosted pages, you only get what you get which is going to vary depending upon when you're reading this message. Here in late 2019, the Cognito-hosted page redirects successful logins and confirmations (of phone/email) to whatever you specified as the redirect URL.
My issue is similar. After the user signs up, I want to customize the CSS of the confirmation page which doesn't appear possible. The confirmation page isn't great because it means that if the user closes the confirmation code entry tab before entering it, then their email is in the system but unconfirmed. And there's no way to confirm it. It's stuck. I'd like to have giant red letters that say "DO NOT CLOSE THIS CONFIRMATION TAB. CHECK YOUR EMAIL FIRST!" but there doesn't appear to be any way to do this at present.
The solution to any of these "how do I customize X of the Cognito-hosted flow" is either (a) look in the available UI customizations or (b) if they aren't available, change to an entirely hosted flow (still Cognito... just using your own pages and URLs).
I'm using Mailchimp's API (v1.3) to add email addresses to a subscriber list on one of our sites. Obviously, I'm using listSubscribe() and everything is working fine, for the most part (read: API call returns true, all of the data I'm sending to Mailchimp gets added/updated correctly).
The problem, however, is that whenever a new address is added, the things that are normally supposed to happen (in particular: email notifications to list manager, addresses showing up in the dashboard list status stream) aren't happening.
I've looked around for quite a bit and haven't found anyone with the same issue. Any ideas?
The default action of listSubscribe to add a subscriber is opt-in. This means that when you submit a listSubscribe the subscribed user will get an email asking to confirm their opt-in.
If the user does not follow the link in the email then they will not appear in the dashboard.
You can bypass this by using:
'double_optin' => FALSE,
http://apidocs.mailchimp.com/api/1.3/listsubscribe.func.php
However this is only recommended for very occasional circumstances (essentially where you are handling the opt-in).
In my case I am not activating a user account until they verify their email address. If let the opt-in email be sent then the user is going to get a number of emails from my web app. I'm being very careful to make sure that they're verifying their subscription and all subscription stuff is being processed by the web app (eg a user unsubscribes within the web app, not via MailChimp).
I talked to the Mailchimp support, and they said those actions won't happen using their public API; there is no way to trigger them.
How have people intergrated custom CRM type applications with email?
I have a Access 2003 front-end application with a SQL Server 2005 backend. One CRM
part of the application tracks the activity with the customer in a traffic
log table. Sometimes the salesstaff has communication with their customer
using email instead. What do people do to synch this up with an application?
I was thinking about creating a form to enter the initial message, so I
could save it into a table and then have the system generate a email, of
course, this doesn't handle the email communication after the initial email.
Thanks
What you need to do is setup your domain name with a free google apps account. Your sales staff can still use the clients of their choice, but since they are essentially using custom gmail accounts, every single email that they send and receive will be recorded in a nice and neat transactional format in the gmail interface. Since your sales staff is always online, they will always have access to every message they ever sent. If you want to have access to the emails, you can set it up that every single message that gets sent are automatically blind forwarded to your account. Filters can be set up to automatically tag and archive them, so you will not be overwhelmed, but you will still be able to search them. Google Apps will also give you a central contact directory similar to outlook/exchange.
Here are a few options for you:
Use web forms for all communications. When a message is sent out, the only thing it includes is a link back to the site. Responses are sent the same way.
Setup an email alias that your sales staff Cc's when they want their correspondence to be tracked. Your app would periodically read a POP mailbox, and record the traffic. Customers would have to remember to Cc the same email box for the traffic to be remembered.
Establish a single common email box, such as sales#domain.com. All outgoing mail is marked as being from that account, so all replies will go through it. To send mail, sales staff uses a web form. Messages are tagged with a key that associates them with a particular customer. Putting the key in the subject header usually works OK (that's how many support ticket management systems work, for example). Replies from customers keep the tag. Your app then reads an associated POP mailbox, parses out the keys, and stores the email accordingly.