CHANGELOG: April 8 / Convert entities to another Type, Zendesk integration, Schema changes in Audit Log

[B_Sp]

Yes, following on - and I suspected to see you in here and discussing what I was intending after my initial cuts at using conversion:

Per this point:

@Oshyan

Interesting, and nice to see initial functionality here. I guess, however, I was hoping there would be field (re)mapping, as in the case of e.g. CSV import, where the UI/UX is actually quite excellent (one of the best CSV import processes I’ve seen in fact). Is that something you plan to add in the future?

I second this, it was also part of one of the original requests:

[DONE] Convert Entity to another Type

Guys, just wanted to try to find out again if you have thoughts on this. I imagine as the user base of Fibery grows I won’t be the only one with this issue. For more context, this is a big piece of Jira, which I’m sure many Fibery converts have dealt with, and because of the massive customization you can do in Jira issues - which in many ways is one of the ways it closely resembles Fibery - there is an actual wizard that does the mapping, you can see it discussed in this article: Here is a hi…

Jira does this well, so does the .csv mapper. Without that, you have a lot of manual work here I’ve found in my few attempts…

Other points on the conversion:

1. I would really like to see a link to the two. Ideally, both 1) an autogenerated comment, and 2) evidence of the original Entity in the activity log. In fact, it would be great if you could decide upon conversion, perhaps on a separate screen that would also do the mapping, what to do with the original:

• keep it open
• close it
• delete it

Right now I have to say that I don’t really see much time savings with this feature vs. doing this manually. There is no mapping, nor any connection between the two entities. So the difference between doing this manually, and converting with this feature we have now, is:

1. Manually I can copy the name of the initial entity, hit “ctrl” + K to create a new one, paste in that name, select the new entity type, and I have a new, unrelated Entity, just like with this feature

2. With this feature, I click “convert to entity,” choose the new entity type, click through the warning page, and then, if I happen to have identically named fields, get the benefit of saving a few more instances of copying manually.

In either case, any connection between the two I am setting up manually. That includes deleting the previous Entity.

So the only real benefit I’m seeing so far with this version of this feature is copying over identically-named fields. A big disappointment is the generic Rich Text field, which is typically “description” in other similar tools to Fibery, won’t come over unless it is named identically across Types. The thing is, I intentionally name my Description fields differently in Fibery, which is something that is a differentiator and a feature I’m glad to have!. But that in turn renders the benefit of this converting of Entities to other types a lot less useful.

Curious @Oshyan if you have other feedback. Another thing I was really hoping for is Bulk Conversion, as we’ve often created a series of entities that turned out was in the wrong Type…

@B_Sp

One situation is we have things that go in as a “Project” and it turns out they are really “Tasks” and need to be changed, but a lot of work has already gone into building the entity.

Thanks and looking forward to the next iteration of this feature, it’s really needed and unfortunately in my opinion we don’t have much usefulness yet…