Hello everybody, I hope someone has a good tip for me on how to solve this issue.
I don't want anybody in my company to use the Outlook function in a sub task, only in the main (parent) task.
This is because Jira gives each issue / task a number and I want to avoid the possibility of my collegues using this feature and maybe communicate a different issue number and confuse the customer. Normally, the title in each external communication includes the issue number, name of the project / product and so on. But if the customer gets different issue numbers, I can already see them being confused.
Hi @Dai Pham , welcome to the Atlassian Community and thanks for your post.
When you say that you want to disable the Outlook integration for only subtasks, do you mean that you don't want to send any notifications for subtasks?
In general, notifications are controlled by a notification scheme, https://support.atlassian.com/jira-cloud-administration/docs/configure-notification-schemes/ which, unfortunately does not allow for the distinction between the type of work item, you either send a notification when something is created, or you don't.
Do you have an app or some other tool you are using to notify people of the activity in Jira? Can you explain that a bit more please so we can understand better what you are trying to do?
Best wishes
Hello Valerie, thanks for the welcome.
"do you mean that you don't want to send any notifications for subtasks?" ... Sort of. Teams and so on is ok, but not Outlook.
Here is the thing... I'm introducing Jira to the whole company and giving introduction to everyone where I highlight the comfort and usability of Jira. One of the features I especially highlight is that people can write Emails and Teams messages directly in / through the issue. And the title of the issue is also the title of the Email they sent or the name of the group chat they start in Teams.
And then one collegue asked me what if we start communicating to our customers through Emails. Before it was just on project ID for the whole communication. Now we have Issue XX which created subtask XXY and XYY and XXY-2 and so on. Imagine there's need to communicate with the customers in every subtasks.... They will be super confused about the different IDs.
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.