From: kashalkar <kiran.kashalkar@riftio.com>
Date: Sat, 11 Jun 2016 13:04:17 +0000 (+0200)
Subject: UI Feature Request: Restructure layout of service primitive page
X-Git-Url: https://osm.etsi.org/gitweb/?a=commitdiff_plain;h=44d0dffd167d677b88b72ca625660c0c7cb7c3da;hp=6fd27b872c78e995ee30fe206d09910159af40c1;p=osm%2FFeatures.git

UI Feature Request: Restructure layout of service primitive page

Change-Id: I66bf5b4fbcdfcdbc65fb8e0888e913b7bd585f51
---

diff --git a/Release1/ui-feature-service-primitive-layout-restructure.md b/Release1/ui-feature-service-primitive-layout-restructure.md
new file mode 100644
index 0000000..30e4d5e
--- /dev/null
+++ b/Release1/ui-feature-service-primitive-layout-restructure.md
@@ -0,0 +1,28 @@
+# Restructure Service Primitive Jobs Layout  #
+
+## Proposer ##
+Kiran Kashalkar (RIFT.io)
+
+## Type ##
+**Feature** (do not modify)
+
+## Target MDG/TF ##
+UI, SO
+
+## Description ##
+Currently the service primitive job details have no order, so one cannot tell
+what order the jobs were executed in.
+With the help of the SO to provide a timestamp (seconds since epoch) on each job indicating the
+submission time, the UI should order the jobs with latest on top.
+The service primitive jobs also don't have the parameters passed along with the
+job, so context is lost.
+Again, with the help of the SO module, the UI should show the parameters that
+were used when triggering a job.
+
+
+## Demo or definition of done ##
+Should demonstrate the following:
+1. When multiple jobs are fired, they should be displayed in reverse order of
+ trigger time. i.e. latest on top.
+2. Each job should display the parameters it was triggered with in addition to
+ current information.
\ No newline at end of file