Ability not to link to end state entities

Ideas & Features
1

Please implement the ability not to show entities which reached end state in the relations.
Think about following use cases:

  1. The Sprint which is completed - what is the reason to keep ability to allow linking features to it?
  2. Think about Epic which is “done” - no sense to allow linking more features to it
  3. Think about “Request” which was fulfilled - no sense to keep allowing linking more tasks, orders, etc to it.

Ideally, should be configurable to relation: something like “Prevent linking when reached end state”.

2

Seems to be an example of this:

3

What will happen with existing relationship once e.g. it’s done? Relationship gone or not showing?

4

Still TBD. I suspect that in the short-term, it will only be possible to set up filters when defining new relationships between dbs, so existing relationships will not be affected. But I’m just guessing.

5

Here’s a decent workaround, that might work for you.

Using Requests as an example you have your Request database and then you create an Arch Request database for archived Requests. When a Request is complete you convert it to an Arch Request and then delete the Request, this can also be handled by an automation.

Note that the Arch Request db should have all the same fields as the Request db and you will need to remember to update the Arch Request db when Request db fields are added or renamed.

6

In case there is any reporting - having data in two dbs will make it much more completed. I don’t see this as a viable workaround :frowning:

7

When constructing a report view, it is possible to report on multiple databases, so it need not be complicated. And if the databases have the same fields, then it is trivially easy to configure.

1 Like