Content
View differences
Updated by Jan Sandbrink almost 11 years ago
### Reproduction
- Precondition: Mails can be sent
- add a work package comment
- use the `##ticketnumber` macro in the **comment**
- refer to a WP in a private project
- maybe: refer to a WP you are not even able to receive yourself
- make sure that a person, that is privileged to see the refered WP, also receives a mail
- save the comment
### Expected
- in HTML mails markup The macro (and other kinds of markup) is resolved properly
- a person that is allowed to see a refered WP does not see `##XXX`, but the resolved macro (e.g. `#XXX: A work package`)
- a person that is not allowed to see a refered WP only sees `##XXX` `#Bug 123: Some subject`)
### Actual
- markup The macro is properly resolved (in HTML mails): **good**
- everyone has unresolved ticket references (`##XXX`) not resolved, the text in their the mail texts: **bad** reads plainly `##ticketnumber`
- Precondition: Mails can be sent
- add a work package comment
- use the `##ticketnumber` macro in the **comment**
- refer to a WP in a private project
- maybe: refer to a WP you are not even able to receive yourself
- make sure that a person, that is privileged to see the refered WP, also receives a mail
- save the comment
### Expected
- in HTML mails markup
- a person that is allowed to see a refered WP does not see `##XXX`, but the resolved macro (e.g. `#XXX: A work package`)
- a person that is not allowed to see a refered WP only sees `##XXX`
### Actual
- markup
- everyone has unresolved ticket references (`##XXX`)