-
Type:
Story
-
Status: Closed
-
Priority:
Major
-
Resolution: Discarded
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Objects
Context:
Some relationships must be in a 1 to 1 relation, a classic example of this relationship would be a citizen and its ID document. The one-to-one relationship also helps the user to build their objects, lets say we have this CitizenInfo, IDdocument objects, and Adress. If we add all the information of the IDdocument and Adress inside of the CitizenInfo one, it would be a massive table with the same permissions and would be much harder for the user to delete their adress and create a new one, or relate the adress with another objects that might be necessary.
Acceptance Criteria
1 - Given an objects admin,
when adding object relationship,
then I must be able to add one-to-one relationships among objects
- For this story we are only considering amog custom objects
2 - Given an objects admin,
when managing objects relationships,
then I must be able to manage the existing one-to-one relationships
3 - Given an objects admin,
when having a one-to-one relationship,
then I must be able to identify in both objects that relationship
4 - Given an objects admin,
when having a one-to-one relationship,
then I must be able to add only as fields in object layouts
- One-to-one should not be a relationship tab in the layout
5 - Given an user,
when adding entries in a object,
then I must be able to relate the entries from both objects
6 - Given an user,
when adding entries in a object,
then I must not be able to relate the same entry with more than one entry in the related object
Definition of Done (DoD):
- All Acceptance Criteria were passed;
- Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
- Validated by QA and Product Manager;
- No critical bug related to Story scope (FP5);
- Make sure that all system documentation were updated (if necessary)
- duplicates
-
LPS-146222 As an object creator, I want to define one-to-one relationships among custom objects
-
- Open
-
- fixes
-
LPS-140091 Relationship field should be created on both objects for a one to one relationship
- Closed
-
LPS-140092 It is possible to relate 2 or more entries with 1 entry on the one to one self relationship
- Closed
-
LPS-140093 Relationship field is filled only in one side of the relation (one to one)
- Closed
-
LPS-140099 It should not be possible to add a one to one relationship tab on the custom layout
- Closed
-
LPS-135399 As an object creator, I want to define one-to-one relationships among custom objects
-
- Closed
-
- is a dependency of
-
LPS-144639 Remove FF of one-to-one relationships among custom objects
-
- Open
-
- Is blocked by
-
LPS-140091 Relationship field should be created on both objects for a one to one relationship
- Closed
-
LPS-140092 It is possible to relate 2 or more entries with 1 entry on the one to one self relationship
- Closed
-
LPS-140093 Relationship field is filled only in one side of the relation (one to one)
- Closed
-
LPS-139598 It is not possible to view a Relationship
-
- Closed
-
-
LPS-139906 Searching for another entry's ID is not working on the Relationship field
-
- Closed
-
-
LPS-139907 Entries are not being listed on the Relationship field
-
- Closed
-
- is related to
-
LPS-135400 As an object creator, I want to define one-to-many relationships among custom objects
-
- Closed
-
- relates
-
LPS-146222 As an object creator, I want to define one-to-one relationships among custom objects
-
- Open
-
- Testing discovered
-
LPS-140099 It should not be possible to add a one to one relationship tab on the custom layout
- Closed