Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FEATURE REQ] Metadata on ChatThreadProperties #24974

Closed
GuidoNeele opened this issue Oct 28, 2021 · 7 comments
Closed

[FEATURE REQ] Metadata on ChatThreadProperties #24974

GuidoNeele opened this issue Oct 28, 2021 · 7 comments
Labels
Client This issue points to a problem in the data-plane of the library. Communication customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@GuidoNeele
Copy link

Library or service name.
What library or service is this request related to? Azure.Communication.Chat

Is your feature request related to a problem? Please describe.
What feature would you like to get added? What problem is it solving?

Being able to store metadata on the chat thread just like what's already possible with chat messages.
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Oct 28, 2021
@jsquire jsquire assigned jsquire and unassigned jsquire Oct 28, 2021
@jsquire jsquire added Client This issue points to a problem in the data-plane of the library. Communication CXP Attention needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team labels Oct 28, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Oct 28, 2021
@ghost
Copy link

ghost commented Oct 28, 2021

Thank you for your feedback. This has been routed to the support team for assistance.

@SaurabhSharma-MSFT SaurabhSharma-MSFT self-assigned this Oct 28, 2021
@SaurabhSharma-MSFT
Copy link
Member

@GuidoNeele We are looking into this and get back to you.

@SaurabhSharma-MSFT SaurabhSharma-MSFT removed their assignment Oct 29, 2021
@SaurabhSharma-MSFT SaurabhSharma-MSFT added the Service Attention Workflow: This issue is responsible by Azure service team. label Oct 29, 2021
@ghost
Copy link

ghost commented Oct 29, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @acsdevx-msft.

Issue Details

Library or service name.
What library or service is this request related to? Azure.Communication.Chat

Is your feature request related to a problem? Please describe.
What feature would you like to get added? What problem is it solving?

Being able to store metadata on the chat thread just like what's already possible with chat messages.

Author: GuidoNeele
Assignees: -
Labels:

Service Attention, Client, customer-reported, question, needs-team-attention, Communication, CXP Attention
Milestone: -

@GuidoNeele
Copy link
Author

Any news on this? Would be a nice addition.

@angiurgiu
Copy link
Member

Thank you for your feedback. We've logged this feature request into our backlog and will consider it in the future.

@ashwinder ashwinder reopened this Feb 16, 2022
@l2aelba l2aelba mentioned this issue May 23, 2023
Closed
@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 4, 2024

Hi @GuidoNeele, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.

1 similar comment
@github-actions GitHub Actions
Copy link

github-actions bot commented Apr 5, 2024

Hi @GuidoNeele, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 5, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Apr 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Client This issue points to a problem in the data-plane of the library. Communication customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@jsquire @GuidoNeele @angiurgiu @ashwinder @SaurabhSharma-MSFT