Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Requirements Tracking

From EGIWiki
Jump to navigation Jump to search

RT

Software homepage - Request Tracker homepage

RT at EGI.eu

Request Tracker instance at EGI.eu - Request Tracker EGI.eu

Authentication - using EGI Single Sign-On (SSO) - EGI.eu SSO

Access - to get access for RT Requirements queue, please send e-mail to ucst at egi.eu including SSO username.

TODO:

  • Ticket creation by e-mail or RT web with SSO
    • All SSO users by default should be able to access requirements queue

Requirements queue updates

2010-12-15 Meeting NA3, SA1, SA2, JRA1

New actions defined to take:

  • Rename: Tools and applications -> User tools and applications Done
  • Rename: Metrics store -> Metrics portal Done
  • Multi-selection lists should be available for tags, some of the categories For Tags is possible, for Categories just for the lowest level
  • Define the mandatory and the optional fields Done. Mandatory: Category (level 1), Requestor (level 1)
  • Non-functional tags should be separated from technology tags on the GUI Done
  • Possibility to add custom tags Done
  • Adding more status values: In progress
    • for requirements queue: new status value - "Accepted"
    • for roadmaps queues: new status values - "Validated"
  • Multiple priorities for a request – requester’s priority, implementation priority Same 0-5 in both types of queues. Same definitions. Decoupling of requirements from features allows the usage of different priorities on the requester and the implementer sides
  • Invite group leaders to check ticket submission interface
  • Open submission interface for the groups
  • New queues: In progress
    • ops-tools-roadmap
    • user-tools-roadmap
  • Re-assign “feature” tickets to feature queues
  • Associate feature tickets with requirement tickets (from the “Requirements” queue)
  • Add “release” tickets to the features queues. Link features tickets to release tickets.
  • Release tickets should have Release date instead of Time Estimated (Can the “Reminder” feature be used for this?)

Requirements categories

Names of the fields implemented in the RT system:

  • Category (level 1)
  • Category (level 2)
  • Requestor (level 1)
  • Requestor (level 2)
  • Requestor (level 3)
  • Non-Functional Tag
  • Technology Tag
  • Custom Tag


Category

Legend:

  • - Category (level 1)
    • - Category (level 2)


  • Support Service
    • Applications Database
    • Training Services
    • VO Services
    • Web Site
    • Other
  • Support Action
    • Consultancy
    • Training
    • Other
  • Unified Middleware Distribution (UMD)
    • Accounting
    • Authentication
    • Authorization
    • Compute
    • Compute Job Scheduling
    • Credential Management
    • Database Access
    • File Access
    • File Encryption/Decryption
    • File Transfer
    • File Transfer Scheduling
    • Information Discovery
    • Messaging
    • Metada Catalogue
    • Monitoring
    • Parallel Job
    • Remote Instrumentation
    • Service Management
    • User Management
    • Virtual Image Management
    • Virtual Machine Management
    • Workflow
  • Operational Tools
    • Accounting Portal
    • Accounting Repository
    • GGUS
    • GOCDB
    • Metrics Portal
    • Network Monitoring
    • Operations Dashboard
    • Operations Portal
    • SAM / ACE
    • SAM / ATP
    • SAM / MyEGI
    • SAM / NCG
    • Other
  • User Tools and Applications
    • Domain specific applications
    • Generic Tools
    • Other
  • Non-Functional
    • (Inter)Operability
    • Availability
    • Installability
    • Performance
    • Portability
    • Recoverability
    • Reliability
    • Safety
    • Scalability
    • Serviceability
    • Usability
    • Other
  • Other


Requestor

Legend:

  • - Requestor (level 1)
    • - Requestor (level 2)
      • - Requestor (level 3)


  • Virtual Research Community
    • Astronomy & Astrophysics
    • Computational Chemistry
    • Earth Sciences
    • eHumanities
    • HealthGrid
    • Hydro-meteorology
    • WeNMR
    • WLCG
    • Other
  • Heavy User Community
    • High-Energy Physics
    • Life Sciences
  • Virtual Organization
    • Astronomy, Astrophysics and Astro-Particle Physics
      • lofar
    • Computational Chemistry
    • Computer Science and Mathematics
    • Earth Sciences
    • Fusion
      • fusion
    • High-Energy Physics
      • calice
      • cdf
      • hone
      • ilc
      • ildg
      • pheno
    • Infrastructure
    • Life Sciences
      • biomed
      • enmr.eu
      • lsgrid
      • vlemed
    • Other
      • desktopgrid.vo.edges-grid.eu
      • vo.complex-systems.eu
    • Multidisciplinary VOs
      • gridmosi.ici.ro
      • nordugrid.org
      • vo.iscpif.fr
      • voce
  • NGI or AERO
    • NDGF
    • NGI_IT
    • NGI_AEGIS
    • NGI_ARMGRID
    • NGI_BA
    • NGI_BG
    • NGI_BY
    • NGI_CH
    • NGI_CYGRID
    • NGI_CZ
    • NGI_DE
    • NGI_FRANCE
    • NGI_GE
    • NGI_GRNET
    • NGI_HR
    • NGI_HU
    • NGI_IBERGRID
    • NGI_IE
    • NGI_IL
    • NGI_MARGI
    • NGI_MD
    • NGI_ME
    • NGI_NL
    • NGI_PL
    • NGI_RO
    • NGI_RU
    • NGI_SI
    • NGI_SK
    • NGI_TR
    • Other
  • Project
    • DRIHMS
    • EGI-InSPIRE
      • UCST
      • EGI Training Working Group
    • ESFRI 28 projects
    • HealthGrid
    • Other
  • Open Grid Forum
  • Other


Non-Functional Tag

  • Feature
  • (Inter)Operability
  • Availability
  • Installability
  • Performance
  • Portability
  • Recoverability
  • Reliability
  • Safety
  • Scalability
  • Serviceability
  • Usability


Technology Tag

  • ARC
  • gLite
  • UNICORE
  • Globus


Custom Tag

Enter any Tag


Status definitions

Requirements queue status values definitions:

  • New = just arrived, no action taken yet (ticket must be Opened)
  • Open = to be discussed (Ticket is allocated to a person/group. This person/group should attach a deadline to the ticket - e.g. when it will be discussed)
  • Stalled = discussion/implementation is on hold for some reason
  • Resolved = solved (validation may or may not have happened. There will be no "validated" status at the moment. If we need, we can add it later)
  • Rejected = EGI discussed then rejected the request (reason of rejection must be attached to the ticket)
  • Accepted = to be implemented (Requested feature/action will be implemented. The owner of the ticket is responsible for the implementation)


ops-tools-roadmap and user-tools-roadmap queues status values definitions:

  • New = Feature that is not necessarily linked to any requirement yet. Feature that is not necessarily allocated to any release yet. (This status can be used for features that need to be discussed, finalised to meet a requirement/request)
  • Open = Feature to be included in the next release (the feature is currently under development). The ticket must depend on at least one requirements ticket from the requirements queue
  • Stalled = Feature to be included in some future release (not in the next release). The ticket must depend on at least one requirements ticket from the requirements queue
  • Resolved = Implemented (validation must follow)
  • Rejected = EGI discussed then rejected the feature (because no related user requirement exists)
  • Validated = The feature has been validated (responsibilities have to be defined)

Priority definitions

  • 0 - Unknown
  • 1 - Low
  • 2 - Medium
  • 3 - Important
  • 4 - Critical

Dashboards

Currently there are Pre-defined RT Dashboards for each of Requestors available on the RT system

All Dashboards

Virtual Research Communities (VRCs)

Existing VRCs

Potential VRCs

VRCs

This Dashboard lists all available requirements in the RT Requirements queue by all VRCs.

VRCs

WeNMR

This Dashboard lists all available requirements in the RT Requirements queue by VRC_WeNMR.

VRC_WeNMR

WLCG

This Dashboard lists all available requirements in the RT Requirements queue by VRC_WLCG.

Astronomy & Astrophysics

This Dashboard lists all available requirements in the RT Requirements queue by VRC_Astronomy & Astrophysics.

Computational Chemistry

This Dashboard lists all available requirements in the RT Requirements queue by VRC_Computational Chemistry.

Earth Sciences

This Dashboard lists all available requirements in the RT Requirements queue by VRC_Earth Sciences.

eHumanities

This Dashboard lists all available requirements in the RT Requirements queue by VRC_eHumanities.

HealthGrid

This Dashboard lists all available requirements in the RT Requirements queue by VRC_HealthGrid.

Hydro-meteorology

This Dashboard lists all available requirements in the RT Requirements queue by VRC_Hydro-meteorology.

Heavy User Communities (HUCs)

This Dashboard lists all available requirements in the RT Requirements queue by HUCs.

HUCs

National Grid Infrastructures (NGIs)

This Dashboard lists all available requirements in the RT Requirements queue by NGIs.

NGIs

Virtual Organizations (VOs)

This Dashboard lists all available requirements in the RT Requirements queue by VOs.

VOs

Projects

This Dashboard lists all available requirements in the RT Requirements queue by Projects.

Projects

Operational Tools

This Dashboard lists all available requirements in the RT Requirements queue by Operational Tools.

Operational Tools

Unified Middleware Distribution (UMD)

This Dashboard lists all available requirements in the RT Requirements queue by UMD.

UMD

NA3

This Dashboard lists all available requirements in the RT Requirements queue by NA3.

NA3

All

This Dashboard lists all available requirements in the RT Requirements queue.

All

New Requirement

RT Web

1) Register for EGI Single-Sign On(SSO) account by going to - https://www.egi.eu/sso/

2) log-in with SSO into RT system by going to - https://rt.egi.eu/ or go directly to one of provided Dashboards i.e. NGIs

2) Go to New Requirement creation interface by pressing "New ticket in" Note: make sure that you choose requirements queue

NGIs.PNG


3) Filling the Requirement details

4) Press "Create" to create the Requirement

Create.PNG

e-mail

Web Form

Subscriptions

1) log-in with SSO into RT system - https://rt.egi.eu/ or go directly to one of provided Dashboards i.e. VOs


2) "VOs Dashboard"

Vos subscription.PNG


3) "Subscription"

Subscription.PNG

Reports

Retrieved from "https://wiki.egi.eu/w/index.php?title=Requirements_Tracking&oldid=7287"