microsoft / microsoft/AzureTRE
Improve Airlock Notifier Emails
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Describe the bug
Airlock import request emails contain a link to the request, but nothing else. The reviewer needs to poke around to find out which project it's for, who requested it, and what they want it for. Without context, it can be difficult to make the right decision. E.g., the same data may be safe to approve for one project, but not for another.
At the very least, the email should contain the workspace name and the name of the person requesting it, so the reviewer can directly contact them if they have a question about the request.
Steps to reproduce
Azure TRE release version (e.g. v0.14.0 or main):
Deployed Azure TRE components - click the (i) in the UI:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Airlock import request email notifier and its existing tests. Update the notification so reviewers can see the workspace name and requesting person's name, then verify the email includes that context alongside the request link.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100