Inline entity creation in Rich Text is very useful, but it has some limitations that prevent it from being much more useful.
Inline entity creation in a Rich Text is not available if:
- more than a single line of text is selected
- the selected text contains an “@”-user reference
There is no way to hook inline entity creation to customize its fields; this must be done afterwards via a normal Rule, and it’s somewhat complicated due to the need to look up the creation Reference, which is also not immediately available.
How could this process be improved?
-
Add a new type of Automation trigger for “Entity pre-creation”, giving the possibility for a script to customize all data being used to create a new entity before it is actually created. The supplied entity Name (markdown) could then be parsed into multiple fields, such as entity Name, Assignees, Due Date, entity Description, etc.
-
The “entity creation context” (i.e. the Rich Text where the entity is being created from) is also key information that allows such a script to perform important functions such as linking the new entity to a specific Story, Feature, etc.