# Tasks Template Status Option

**URL:** <https://community.anytype.io/t/tasks-template-status-option/4369>\
**Category:** Closed\
**Created:** [January 20, 2022, 10:36pm UTC](https://community.anytype.io/t/tasks-template-status-option/4369 "2022-01-20T22:36:01Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![lynxlove](https://community.anytype.io/user_avatar/community.anytype.io/lynxlove/32/1139_2.png) [@lynxlove](https://community.anytype.io/u/lynxlove)\
**Post date:** [January 25, 2022, 3:49pm UTC](https://community.anytype.io/t/tasks-template-status-option/4369/6 "2022-01-25T15:49:57Z")

</div>

Did you every add those status in a different type or page for testing purposes? If you did, they are stored as one possible value of that relation as each relation is presently global and does not limit to a type. The team said they’ll work on adding type qualifier to relations as requested here

> [@Ability to limit the scope of a relation](https://community.anytype.io/t/ability-to-limit-the-scope-of-a-relation/1553):
>
> Is your feature request related to a problem? Please describe. The add relation pop-up in the create type view lists all the relations across all object types, even the ones such as the camera, camera aperture, camera exposure & rotten tomato scores, etc. These relations are tightly coupled to an objects type. A rotten tomato score is not applicable to any type except a media or a web series. Same goes for the camera exposure relations which is only applicable for the image type. Sin…

So that should solve this problem by allowing user to create separate status relation for each types.

---

_[View the full topic](https://community.anytype.io/t/tasks-template-status-option/4369)._