I'm subscribed to an issue in JIRA. Whenever someone comments on it, or changes a comment of his, I get an email.
Often this results in multiple consecutive emails, when people enter a comment, and then refine it multiple times.
I'd like to tell JIRA to wait after a new comment before sending me the notification mail, which should then include all modifications to it by the time.
Is this possible?
I know this question might be better off at superuser, but the jira tag here seems by far more frequented.
If I get you right, when somebody wanna edit his comment there is a tick asking if he wanna notify all the watchers about the edit with the email message or not.
So all you can do is to ask your team to leave comments with 'notify' tick disabled
You can actually disable this autosend notifications through the API from Jira, see documentation : https://confluence.atlassian.com/jira/configuring-email-notifications-185729575.html
Related
I am using a jira mail handler to automatically create tickets whenever email comes to a particular mail id. However many of the users who are sending mails are part of jira users and jira will create the issue with creator as their name. Later looking at the tickets is there any way to identify whether the ticket was created from email or the user manually created it. Thanks in advance
I think, it is not possible automatically. What about using a extra customfield? this way you can fill that new field, with the value you want: one for manually opened tickets, and another for email opened tickets. You can show or hide this field, and this would allow you to look for manually opened using jql (even it is not your first need :) )
For making it more visual, then you can use a bit of proggramatic magic and represent the values with icons or wahtever.
Let me know if it is not clear or if you need help for adding the new field or whatever.
Edit: the easiest way for doing this could be add to every issues opened by mail, at the begining of the summary something like "from mail:" and then the real summary. Anyway probably better if you customize the handler or create new one
Regards
We are running JIRA 4.1.1 and had an employee who moved elsewhere in the company. We still need his issues in JIRA so we can't completely removed him. Is there anyway to make it so he won't still receive emails/notifications?
I need a solution other than changing the email to an unused or invalid email address, because this will start eating up log space in JIRA
Thanks.
If he moved to another role, his tasks and responsibilities should have been taken over by someone else.
Make a bulk edit and assign that new user to the given issues.
With bulk edit, you can change reporter also.
I looked through the questions and found a question somewhat related but it wasn't the same.
If you use the event_list_attendees api call you get back a list of attendees. Those attendees have a modified field. One of the possible parameters in the api call is modified_after.
My question is regarding what triggers the modified field to update? Is this a user profile related field or is it related to this particular event ticket purchase? The api describes these two as the following:
modified_after Return only attendees whose “modified” value is equal
to or after this date/time (e.g., “2013-01-28 00:00:00″)
modified The date and time the event was last modified, in ISO 8601
format (e.g., “2007-12-31 23:59:59″).
Perhaps to explain why I am wondering what triggers modified to update. The goal is to create a small, one day use, mobile website that will allow users to see who has shown up so far for a local event I am working with. I know the api does not directly support this functionality. In my case however "close enough" is "good enough". If someone's ticket being scanned at the door triggers the modified field that would be sufficient.
So, does it?
Great question!
The modified attribute relates only to the individual attendee in the order. So, it won't be triggered by the account wide profile changes for that respective user. However, if a user logs in to Eventbrite and changes the information that specifically relates to this event (example: they change the spelling on their last name for this specific order).
Alternatively, you can actually use /event_list_attendees and set "display_full_barcodes" to "true" to see the status of the barcodes. When the barcode is used, you'll know that someone has been scanned in.
If you come up with a cool hack, then we'd love to check it out!
Hope that helps!
I've been looking for a way to have a user acknowledge a
ticket after it has been assigned to them. I don't know if
this is a built in feature or if there is a plugin that
will create a state/button for a user to accept a ticket
after it has been put in there queue. I would expect to
see something like this from the ticket window around
workflow or start progress but no amounts of digging
through configuration settings has turned anything
relevant up.
Does anyone know about this added functionality in JIRA?
Much thanks.
I did this by a custom workflow step. After an issue arrived to an assignee (with status New) he/she should move it to another step (with status Open). Until he/she does it, the issue is considered as not noticed/reached the assignee. Also I have had a report showing issues with New status for more than a predefined period of time.
I'm not aware of a ready-made plugin which performs similar task (perhaps, I should dig into my posts on Atlassian answers to discover some clues for other solutions).
As #Stan says above, a custom workflow is the way to implement this. The workflow functionality in JIRA is very flexible and as a result has a bit of a learning curve, but Atlassian's documentation is pretty good. Post back here if you need help.
I have an blog where anyone can comment. I would like to approve the comments before they are published. I have a boolean field named "published" and I'm unsure what to do next. Can anyone point me in the right direction?
I can imagine several features :
you need to be be notified when a comment is created. If you're not expecting too much traffic, the application can notify you by email with the ActionMailer
you need an admin page where you'll see all the comments that are waiting from your approval. Use filters to ensure that only you have access to this page.
you'll certainly need to see the comments "in situ" before approving them. The blog page should display only "published" comments for average user, but for you it should display all comments, with a button to publish the ones waiting for approval.