[MGNLCDEP-80] Link node paths in dependencies tab Created: 29/Apr/15  Updated: 15/Apr/16  Resolved: 13/Jul/15

Status: Closed
Project: Content Dependencies
Component/s: None
Affects Version/s: 1.4.2
Fix Version/s: 1.4.3, 1.5.1

Type: Improvement Priority: Neutral
Reporter: Frank Sommer Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: UX, support
Remaining Estimate: 0d
Time Spent: 1d 4.75h
Original Estimate: 0.75d

Attachments: PNG File Desktop02_22_DialogAW7_Semantic layer.tabs.png     PNG File Screen Shot 2015-07-13 at 15.03.12.png     PNG File dep-tab.png    
Issue Links:
Relates
relates to MGNLCDEP-87 Dependency aware confirmation action ... Closed
dependency
depends upon MGNLCDEP-76 Allow for checking dependencies to an... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Sprint: Sprint 2 (Kroměříž)
Story Points: 2

 Description   

The node paths in the dependencies tab should be linked to the corresponding app with selected node.

With the current behaviour the editor must find the app and the location by its self to possible publish the missing asset.



 Comments   
Comment by Federico Grilli [ 21/Jul/15 ]

Sorry for reopening. It's nothing related to code or QA but I think this improvement is tightly related to MGNLCDEP-76 (which is ongoing) and actually should depend on it. As the latter will allow for checking dependencies to any workspace, this improvement should take that into account rather than hardcoding dependencies to website and dam.

Comment by Philip Mundt [ 22/Jul/15 ]

fgrilli I think it should be the other way round. This improvment is less intrusive and actually uses the old fields, whereas MGNLCDEP-76 introduces new fields. I believe MGNLCDEP-76 should depend on this issue.

Comment by Federico Grilli [ 22/Jul/15 ]

pmundt What I mean is that once MGNLCDEP-76 is integrated (the two issues have also the same fix version) the solution proposed here would become immediately outdated as it keeps on using hardcoded references and doesn't take into account the fact that one will be able to configure any workspace to check for dependencies. That's why I think MGNLCDEP-80 should be solved in the light of MGNLCDEP-76.

Comment by Jaroslav Simak [ 22/Jul/15 ]

Once MGNLCDEP-76 is resolved and integrated, i'll update code of DependenciesField to reflect those changes.

Comment by Federico Grilli [ 22/Jul/15 ]

Generated at Mon Feb 12 00:12:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.