Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

application-specific object overview with all references in scenario steps #60

Closed
bruderol opened this issue Nov 5, 2013 · 2 comments
Closed
Assignees
Labels
complexity:4-Epic Complexity "Epic" --> to be split further into sub stories type:Feature Feature

Comments

@bruderol
Copy link
Member

bruderol commented Nov 5, 2013

As users we want to see all references of a selected application-specific object (e.g. Service call, simulation config, user type etc.).

  • When a user selected an application-specific generic object (as a link in the application) he will navigate to an object overview page where the following things are presented:
    • Details of the selected object (all fields)
    • All references of this object (in a collapsable and filterable tree, starting with use cases inside which the object is referenced, with all scenarios, pages, steps etc. where this object is referenced).
    • By clicking on any of the objects (e.g. the steps) the user may jump directly to the place where the browsed object is referenced (e.g. to a step, a page, etc.).

Implementation-Details:

  • The rest service for getting all data for such an object overview was already implemented.
@emjion
Copy link
Contributor

emjion commented Jul 4, 2014

"By clicking on any of the objects (e.g. the steps) the user may jump directly to the place where the browsed object is referenced (e.g. to a step, a page, etc.).".

-> To what place should be jumped, when a non-scenarioo object e.g. "Feature" will shown?

@emjion emjion added the epic label Jul 15, 2014
@emjion
Copy link
Contributor

emjion commented Jul 15, 2014

Partially implemented. Rest is planned in separate stories.
Reviewed and planend with @bruderol

@emjion emjion closed this as completed Jul 15, 2014
adiherzog pushed a commit that referenced this issue Mar 7, 2016
adiherzog pushed a commit that referenced this issue Feb 3, 2017
adiherzog pushed a commit that referenced this issue Feb 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity:4-Epic Complexity "Epic" --> to be split further into sub stories type:Feature Feature
Projects
None yet
Development

No branches or pull requests

3 participants