Skip to content

show if scenario is part of an ensemble #19

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.

Sign up for GitHub

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

Jump to bottom
Open
klarareder opened this issue Nov 2, 2018 · 2 comments
Open

show if scenario is part of an ensemble #19

klarareder opened this issue Nov 2, 2018 · 2 comments
Assignees
@MGlauer
Labels
metadata OEP metadata not-actionable currently not in a state to allow implementation requirement_specification Pflichtenheft specification_sheet Lastenheft Time-S estimated time to work off, voted on in project meeting Urgency-M urgency level, voted on in project meeting

Comments

@klarareder
Copy link
Contributor

As a user, I would like to be shown whether the scenario is part of an ensemble in order to not overlook the other ensemble scenarios.
@klarareder klarareder added the specification_sheet Lastenheft label Nov 2, 2018
@christian-rli
Copy link
Contributor

Still requires a proper definition of Ensembles.

RequirementSpecificationID=37

@christian-rli christian-rli added requirement_specification Pflichtenheft Time-S estimated time to work off, voted on in project meeting Urgency-M urgency level, voted on in project meeting labels Jan 28, 2019
@christian-rli christian-rli assigned wingechr and MGlauer and unassigned Ludee Jan 28, 2019
@christian-rli christian-rli added the metadata OEP metadata label May 14, 2019
@han-f
Copy link
Contributor

han-f commented Aug 3, 2020

This needs to be pending pending until we know exactly what is a scenario and what data belongs to it. @wingechr and I discussed that proper tagging may help to find (and "bundle") related data. Tagging functionality (even if not working yet) seems to be available for factsheets in general.

@han-f han-f mentioned this issue Aug 3, 2020
Open
@wingechr wingechr added the not-actionable currently not in a state to allow implementation label Aug 19, 2022
@wingechr wingechr removed their assignment Feb 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MGlauer MGlauer

Labels
metadata OEP metadata not-actionable currently not in a state to allow implementation requirement_specification Pflichtenheft specification_sheet Lastenheft Time-S estimated time to work off, voted on in project meeting Urgency-M urgency level, voted on in project meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@wingechr @MGlauer @Ludee @han-f @christian-rli @klarareder