Skip to content

Allow support_bot assign epics from ancestor groups

Felipe Cardozo requested to merge issue_300513 into master

What does this MR do and why?

Allows assigning issues to epics when creating service desk issues using quick actions on description templates.

Instead of raising support bot role to reporter on groups we allow it to only :read_epic when group has at least one project with service desk enabled.

related to #300513 (closed)

How to set up and validate locally

  1. Setup incoming email on your localhost following these instructions.
  2. Create a group and create epic X on it
  3. Create a project within the group and enable service desk on it.
  4. Add an issue description template to the project with a quick action assigning any issue to epic X: /epic EPIC_X_IID
  5. On the project settings configure service desk to use the description template added on the previous step
  6. Send an email to the project service desk address to create an issuse

Expected: A service desk issue should be created an assigned to epic X.

obs: I am having trouble to configure incoming email on my localhost. For some reason EmailReceiverWorker is not taking jobs from sidekiq queue, I had to execute it manually with EmailReceiverWorker.perform_async(raw_email) to verify this. Some other team members are also having the same problem, I will try to investigate what is happening.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Felipe Cardozo

Merge request reports