Relationship between item revisions and Requets

by Francisco Jose Gallego on May 17, 2018

Relationship between item revisions and Requests is made wrongly when the Request differs

  • My "complaint" is about Dimensions behaviour when relating ítem revisions with a Request.

    Scenario 1

    For the first revision 1 of an item, when it is created, I relate it with a Request RQ_ 1. The relationship is establisshed In Response To with this Request. Then, I create a new revision 2 for this item and I relate it with the same Request RQ_ 1. This way, the relationship between revision 1 and Request RQ_ 1 is changed to Affected and revision 2 is related In Response To with Request RQ_ 1.

    Dimensions works fine as both revisions has a relation with Request RQ_ 1, one in Affected and the other In Response To. Both revisions were created because Request RQ_ 1 was required, they (both) have to do with RQ_ 1.

    If you query, you select Request RQ_ 1, two revisions appear, both revisions are related. And it is OK because revisions 1 and 2 were required for Request RQ_ 1. The "effort" to solve Request RQ_ 1 cost two revisions (revisions 1 and 2).

    This scenario 1 is absolutely OK.

    Scenario 2

    For the first revision 1 of an item, when it is created, I relate it with a Request RQ_ 1. The relationship is established In Response To with this Request. Then, I create a new revision 2 for this item and I relate it with a different Request RQ_ 2. This way, Dimensions relate revision 1 with Request RQ_ 2 as Affected and revision 2 is related In Response To with Request RQ_ 2. Of course, revision 1 is kept related In Response To with Request RQ_ 1.

    Dimensions should not have related revision 1 with Request RQ_ 2 because this revision has nothing to do with this Request. Revision 1 was created because Request RQ_ 1 required it but not Request RQ_ 2 which is required just for revision 2.

    If you query, you select Request RQ_ 2, two revisions appear, both revisions are related but, I repeat, revision 1 has nothing to do with this Request. It seems that revisions 1 and 2 were required for Request RQ_ 2 and it is not true!!!!! Only revision 2 should have been related to Request RQ_ 2. The "effort" to solve Request RQ_ 2 cost just one revision (revision 2) and not two revisions (revision 1 and 2).

    This scenario 2 is wrong (in my opinion), Dimensions does not do it as it should.

    Conclusion

    Dimensions should distinguish between what Request an item revision is related to: if when an item revision is created (revise item or checkout) it is going to be related with the SAME Request that the revision is based on, both relationship (Affected, In Response To) must be made but if it is a DIFFERENT Request, just one relationship should be made.

    Ideas

  • Please login to view any attachments.

  • There are no user comments for this idea.
     

PrintEmail

Recent Tweets