Every time I attempt to change ownership of an existing PM to an email address not in our system, I get an error rather than a new staged user being created. As I enter the email address, the autocomplete dropdown with the envelope icon option does appear and I do select just as I would with a creating a staged user from a new PM, but in the Change Ownership popup it appears as if this functionality does not work for some reason.
It’s not possible to change ownership to an email address. You need to change ownership to an actual user.
OK, so the issue is not creating a staged user prior to ownership change, it’s doing an ownership change with a staged user at all.
Is this a technical limitation or a design decision about how staged users should function with regard to content ownership? If a staged user can properly own a PM that they initiated themselves via email, then they shouldn’t they be able to own other messages created via other means (if all messages are treated equally)? I suppose the ownership change procedures might not support the staged user case, but if the relative effort was not too high, I would vote for this to become supported.
For context, the use case with our organization is a help desk group with messages submitted to it that are either:
- Emails forwarded through a non-standard/non-parseable forward format (i.e. an email notification forwarded from a partner’s separate ticketing system), or
- Emails that come from non-email-based origins (i.e. a tweet or facebook message or typeform notification email)
Being able to change ownership to a staged user (especially a newly staged user) would allow much quicker and simpler fixing of the associated contact (so that we can then immediately begin conversing with them), as well as aligning the functionality of the dropdown in Change Ownership with the dropdown in the PM composer (the autocomplete suggestion with the envelope icon).
Unless I’m missing something, right now the only workaround is to copy and paste the body into the bottom of a new PM sent to their email and then to archive/delete the original forwarded message thread, is that correct?
1 个赞
这方面有新的见解吗？
我们偶尔会遇到这种情况：需要创建一个新的暂存用户，然后将其指定为代表他们创建的主题的所有者。
有没有什么快速简便的方法可以实现这一点？
创建暂存用户的最佳方法是启动一个发往暂存用户电子邮件地址的 PM。然后，一旦创建了暂存用户，您就可以对其进行任何您需要进行的操作。
除了将其分配给帖子。除非我做错了什么，否则我似乎无法使用暂存用户来做到这一点。
啊，是的。无法将帖子的所有权更改为暂存用户。对此造成的困惑感到抱歉。暂存用户能做的事情非常有限，因为它们不是“真实用户”，直到他们登录。
您能告诉我更多关于您的用例吗？
我们偶尔需要代表我们的客户创建服务工单。我们的大多数服务和支持客户仅作为暂存用户存在于我们的 Discourse 中。
由我们中的一个人创建帖子，然后将该主题的所有权转移给相关客户，将是最省事的做法。
如果有一种不涉及尝试通过 API 创建主题的方法，我可以转告我们的支持团队，我很乐意这样做。
我只需要能够编写一份包含步骤的内部文档，其中不能包含诸如“SSH 进入服务器并…”之类的操作。
1 个赞
这是一个有趣的情况。也许对于这类情况，需要将模拟用户视为真实用户。
1 个赞
我不确定您在这里建议的是什么。是我能做到的事情，还是功能升级？
抱歉！我手机的自动补全功能经常出卖我！
我已经修复了。
我已经将功能请求转达给员工体验团队，但不确定它是否会实现，因为它涉及到对分阶段用户系统进行大规模的改造。
您是否考虑过“取消分阶段”这些用户？目前这可以通过命令行完成，我知道这不是您想要的。
cd /var/discourse
./launcher enter app
rails c
User.find_by_email("itsmedebryc@yahoo.com").update(staged: false)
也许在用户管理页面添加一个取消分阶段的按钮是我们正在寻找的功能。
我想到的另一个主意……服务单是否绝对需要由客户“开始”？为什么不直接从您的群组收件箱开始创建工单（私信），并包含他们的电子邮件地址？这样您就是作者，他们也参与其中。
我不想取消暂存他们，因为我不想让他们接触到他们可能不感兴趣的摘要电子邮件等内容，除非他们在我们的论坛上创建自己的帐户。
我们不使用私信，我们使用分类主题。如果有一种方法可以将他们添加到主题中，我将非常乐意。
此主题在上次回复后 30 天自动关闭。不再允许回复。