©2017 by AGILIST.Ai Pty Ltd

CHANNEL DATA SOURCES

 

PURPOSE

  • Neelix Approach Grid, Deep-Dive Inspection, Delivery Curve and  Retrospective Actions are designed to be capable of aggregating issues from multiple sources

  • In addition, Contextual Search is also capable of quickly finding concerns that span channels traditionally external to each other; Imagine having a Jira issue and the related Github ticket come up together in the same search

  • Channel data sources are presets configured centrally, and then re-used throughout Neelix

HOW TO ACCESS CHANNEL DATA SOURCES CONFIGURATION

  • Click on Quick Links menu situated in the header

  • Select "Channel" option

UNDERSTANDING CONFIGURATION OPTIONS

  • Baser URL or Repo

  • Provider; Currently Jira and Github are supported; Lodge a request for other channels

  • Entity and Scope; Current support is only for Tickets Search

  • Search Criteria; This can be Jql for Jira or Github api search criteria

  • Story Points (including a tag text pattern setting if the field is a Label)

  • Optional Remaining Points fields (including a tag text pattern setting if the field is a Label)

  • Optional default points value if missing from the source