Using the schedule activity section at the bottom of an email sent from manage case doesn't file the scheduled activity on the case
Not so much a bug it's just my expectation would be that if I'm sending an email from manage case I'd expect the scheduled followup to also be filed on the case.
- Go to the manage case screen for a case.
- Expand the roles section.
- Click the email icon to start an email to one of the people there.
- Fill it out.
- At the bottom expand the schedule followup section.
- Fill it out. Can leave assignee blank it's not relevant.
- Send the email.
- Look at the activities on manage case - the scheduled activity is not there. Where is it? It's on the logged in user's contact on their activities tab (and the email recipient's activities tab).
Using the scheduled followup section when editing a case activity does file it on the case. So this is a little inconsistent.
Activity
added comp:CiviCase sig:bug triaged labels
mentioned in issue #1750 (closed)
Hi,
Thank you for raising an issue to help improve CiviCRM. As you may know, this issue has not had any activity for quite some time, so we have closed it.
We would like you to help us to determine if this issue should be re-opened:
- If this issue was reporting a bug, can you attempt to reproduce it on a latest version of CiviCRM?
- If this issue was proposing a new feature, can you verify if the feature proposal is still relevant? Did it get the concept-approved label? Have other people also shown interest? Could it be implemented as an extension?
If the answer to either question is yes, please feel free to comment or re-open the issue. Please also consider:
- Is it something that you could help implement, either by sending a patch or hiring someone who can?
- Would you be willing to fund the work, either through a CiviCRM partner, or the Core Team?
Thank you for your help and contributions to CiviCRM.
P.S. This is an automated message, see
infra/gitlabissue 20. We understand that automatic responses are annoying, but given the number of open issues as the project evolves, we need a bit of help to triage and prioritise the most relevant issues.-
Hi,
Thank you for raising an issue to help improve CiviCRM. As you may know, this issue has not had any activity for quite some time, so we have closed it.
We would like you to help us to determine if this issue should be re-opened:
- If this issue was reporting a bug, can you attempt to reproduce it on a latest version of CiviCRM?
- If this issue was proposing a new feature, can you verify if the feature proposal is still relevant? Did it get the concept-approved label? Have other people also shown interest? Could it be implemented as an extension?
If the answer to either question is yes, please feel free to comment or re-open the issue. Please also consider:
- Is it something that you could help implement, either by sending a patch or hiring someone who can?
- Would you be willing to fund the work, either through a CiviCRM partner, or the Core Team?
Thank you for your help and contributions to CiviCRM.
P.S. This is an automated message, see
infra/gitlabissue 20. We understand that automatic responses are annoying, but given the number of open issues as the project evolves, we need a bit of help to triage and prioritise the most relevant issues.
