Details
-
Suggestion
-
Resolution: Done
-
328
-
146
-
Description
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hello everyone!
We are excited to let you all know that we've completed rolling this change out, and everyone should have access to it now. For more information about the feature, please refer to the details provided here.
With this update, we will be closing this ticket. We hope we can continue making Jira Software better for you!
Thanks,
Amira Badran,
Product Manager, Jira Software Team
Hi everyone,
We are excited to let you all know that this feature is now in progress, and we will We'll keep you updated on its development and release time. I am eager to hear your thoughts on why you believe this feature will be useful and the specific use cases for it. Please feel free to schedule some time with me to discuss this further. I look forward to chatting with you https://calendly.com/amirabadran/30mins
Amira Badran,
Product Manager, Jira Software Team
Hi everyone,
Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; however, there are not currently any plans to implement this suggestion.
Please make sure to check out:
- a free third party plugin JIRA Watcher Field for JIRA Server customers.
- a free Atlassian Labs plugin JIRA Autowatch for JIRA Cloud customers.
Another alternative is to use "@mentions" in the description of an issue to notify end users about the issue being created, and the recipients can then decide if they want to watch the issue.
Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
Original request description:
As a Project Manager, I want to make sure that respective team members (including me) are informed about new issue creation and depending on an issue type are automatically added as watchers. I want this action to become inseparable from issue creation so that the original issue reporter does not have to inform anyone about issue creation manually. I want to be able to control the watchers' list and nominate the users.
Workaround
Workaround using Automation. Please keep in mind your Automation service limits when using.
1. Create a new custom field of type User Picker (multiple users) and call it something like Add to Watchers List
2. Add the new custom field to your issue's Create screen
3. For the next step you will need your new custom field's ID - you can find this by going to https://<your site name>.atlassian.net/rest/api/3/field, which returns JSON data of all your custom fields and their IDs.
Another way to find your custom field's ID is to go to Settings > Issues > Custom Fields and search for the new custom field you created. Click the three dots [...] next to the field and select Contexts and Default Value. The URL you are taken to will have the field ID in the URL. In the following example, the ID is 10030
https://<your site name>.atlassian.net/secure/admin/ConfigureCustomField!default.jspa?customFieldId=10127
4. Create an Automation rule like so:
5. The smart value in the Add Watchers action should be entered like so:
{{customfield_<insert ID from step 3>}}
Here's how mine looks:
6. Now on the issue create screen I can select multiple users from the Add to Watchers List, and the automation rule will automatically add them as watchers to the issue.
Attachments
Issue Links
- duplicates
-
- Closed
-
- Closed
- is duplicated by
-
- Closed
- is related to
-
- Closed
-
- Closed
-
- Closed
-
- Future Consideration
- relates to
-
JRACLOUD-37637 CC'ed Watchers do not receive notification of Issue Creation (via email)
-
- Closed
-
-
- Closed
-
- Closed
-
- Closed
- was cloned as
-
- Closed
- is action for
-
ERAI-584 Loading...
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
