# September 14, 2023 / 👍 Emoji reactions in comments, experimental Views creation via AI

**URL:** <https://community.fibery.io/t/september-14-2023-emoji-reactions-in-comments-experimental-views-creation-via-ai/5148>\
**Category:** Changelog\
**Created:** [September 14, 2023, 10:42am UTC](https://community.fibery.io/t/september-14-2023-emoji-reactions-in-comments-experimental-views-creation-via-ai/5148 "2023-09-14T10:42:29Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![Robert\_B](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/robert_b/32/7198_2.png) [@Robert\_B](https://community.fibery.io/u/Robert_B)\
**Post date:** [September 16, 2023, 12:30pm UTC](https://community.fibery.io/t/september-14-2023-emoji-reactions-in-comments-experimental-views-creation-via-ai/5148/21 "2023-09-16T12:30:54Z")

</div>

Another mega-hack! Fibery should hire you. 🙂

I like the solution you’ve created. We have the foundation of our back-n-forth comms setup inline - for complex topics/agendas I find it much easier than having separate comments or comment bubbles. I think it’s because visually it helps me to view things in context - like often in the same place structurally as a previous sentence, paragraph, or image - but without disconnecting into a bubble or comment located elsewhere.

We have a decent solution though I’m always thinking if there’s a way to represent who wrote what graphically. Maybe a way to precede text with a user emoji to show who wrote it. But then how to track who read what with multiple users!?

It gets complicated. You have a good solution.

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [September 20, 2023, 7:52am UTC](https://community.fibery.io/t/september-14-2023-emoji-reactions-in-comments-experimental-views-creation-via-ai/5148/22 "2023-09-20T07:52:50Z")

</div>

This is impressive, but also complicated. We are thinking now how to add something like channels with minimal effort from our side. I hope we will have better solution for this use case in few weeks.

---

<div class="post-metadata">

**Author:** ![Marloes](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/marloes/32/5926_2.png) [@Marloes](https://community.fibery.io/u/Marloes)\
**Post date:** [September 22, 2023, 8:04am UTC](https://community.fibery.io/t/september-14-2023-emoji-reactions-in-comments-experimental-views-creation-via-ai/5148/23 "2023-09-22T08:04:33Z")

</div>

_Is it getting boring arealdy when I keep saying “Fantastic Release”? 🤣_

I just converted an entity from one database to another. In doing so, I noticed that Emoji responses in comments are not included. Is that correct?

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [September 22, 2023, 9:41am UTC](https://community.fibery.io/t/september-14-2023-emoji-reactions-in-comments-experimental-views-creation-via-ai/5148/24 "2023-09-22T09:41:35Z")

</div>

> [@Marloes](#):
>
> I just converted an entity from one database to another. In doing so, I noticed that Emoji responses in comments are not included. Is that correct?

Yes, indeed reactions are not preserved when you convert entity, we have a bug for that

---

<div class="post-metadata">

**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\
**Post date:** [September 27, 2023, 1:49pm UTC](https://community.fibery.io/t/september-14-2023-emoji-reactions-in-comments-experimental-views-creation-via-ai/5148/25 "2023-09-27T13:49:23Z")

</div>

> [@mdubakov](#):
>
> AI can create relatively complex filters that are not possible to create via UI. For example, if you have Features and Bugs, you may ask it to `Show all features that have at least two open bugs`, and it will create a filter based on bugs collection filter (which is not possible via UI).

Will it be possible to view and modify the more advanced queries created by AI as texts. I can imagine wanting to make modifications over time where it would be helpful for more advanced users to have see the actual query.

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [October 2, 2023, 2:45pm UTC](https://community.fibery.io/t/september-14-2023-emoji-reactions-in-comments-experimental-views-creation-via-ai/5148/26 "2023-10-02T14:45:04Z")

</div>

Ok thank you @mdubakov, my suggestion of the feature is here:

> [@Next iteration of Comments - Commenting when Resolving & assigning as tasks/reminders](https://community.fibery.io/t/next-iteration-of-comments-commenting-when-resolving-assigning-as-tasks-reminders/527):
>
> Hi once more, I wanted to make some suggestions for comments as you guys evolve them. This is coming mainly from my extended use of a ton of apps in the last several years, and none seem to be able to pull all the best methods for implementing comments all in one place. You guys have a good chance to do that now! Resolving Comments I’ve seen a great way to close out comment resolutions in some apps where they will prompt an extra comment around the “resolve” action. In most cases, you can…

Most important I think would be the ability to comment around the resolution, so instead of just clicking “Resolved” the user can see what was done to resolve it, which is very useful. Jira has a feature you can turn on that you may be familiar with which forces a “resolution” to an issue, which is basically just commenting on what was done when something was closed. I think it would be great to have this too, for example the option to force a comment when marking an entity in a “final” stage of workflow.

As always thanks for the consideration!

[Previous page](https://community.fibery.io/t/september-14-2023-emoji-reactions-in-comments-experimental-views-creation-via-ai/5148.md?page=1)
