Remove test elements from Task objects Status

Describe the bug
The Status relation of newly created Tasks always includes elements like “test”, “test2”, “test3”, “test3”. They can be deleted in a specific tasks, but reappear with every new created Task object.

To Reproduce

  1. Create an account in Anytype with pre-installed types and relations.
  2. Create a new object of type Task.
  3. View the available options for the Status relation.

Expected behavior
I expect the Statuses to include relevant options, and (that’s more of a feature request) be able to edit the pre-installed templates to include only elements relevant for me

System Information:

  • OS: macOS 12.3.1
  • Device Manufacturer/Model: Apple MacBook Pro 2017 13" with touchbar
  • Anytype Version: 0.25.0

Additional context
Here’s a screenshot of a newly created element of type Task:

Hi @pavel, could you check whether this topic describes the workaround (I wouldn’t call it a solution) to your problem?

Hi @sanbouver! Yes, indeed, that workaround works for single tasks, but unfortunately that doesn’t delete these options in the template, so I would have to delete these options manually in every of my tasks. For now, I’ll just stick with ignoring those options. :sweat_smile:

1 Like

Perhaps an option could be included in these relations to only show opties used in current object type?

For example if you use Genre (a Tag relation) in multiple types like a Movies type and a Games type.

In games you use Shooter, Strategy and Racing and in Movies you use Action, Adventure and Sci-Fi.

Now you will see all all of the above when you use this relation:

  • Shooter
  • Strategy
  • Racing
  • Action
  • Adventure
  • Sci-Fi

When you check: “Only show options used in current type” for games you will only see:

  • Shooter
  • Strategy
  • Racing

And for Movies you will only see:

  • Action
  • Adventure
  • Sci-Fi

How do you find others not used when you want? Simple, when you start searching those options will start showing up as well. This would only affect what you first when as shown in the screenshot above in the post from pavel

That seems like a good idea, but I’m afraid that specifying an Object for every tag would be quite tiresome. For example, if I want to add another Genre, I would have to specify in which Types it can be used (game, movie, book, music, etc.)

My opinion is that most relations should be Type-specific and unavailable to other types, since most relations are used in only one type or require different options for different types. The example with Genre displays this problem very well, I would never need a “Shooter” option for a movie. I propose an option to be able to specify if a Relation is global or type-specific. For type-specific Relations, in the “All Relations” tab we can just add the type name in brackets, for example Genre (Movie), Genre (Game), Genre (Music). At the same time, there should be an option to create global relations (something general like “parent”, “used in”, “includes” etc.).

Another addition to this would be one-time relations. For example, when creating a knowledge graph for some very specific topic, I would need some non-typical relations that I won’t be using in the future and don’t want to appear in my Relations list. In this case, I would like an option to either make this relation global or one-time, with the ability to create type-specific relations only in template editor.

Moreover, if I ever feel the need to make a relation Global from Type-specific or One-time, I should be able to do so, for example from the “Relations” tab, where all relations are divided by types.

Edit: I have visualized what I was thinking of (sorry for the artistic style :sweat_smile:):