Input Streams () enable business and quality teams to work in seamless cadence with the Agile development team. Using Micro Focus Connect, Input Streams allow you to pull in external Requirements and Defects into the Rhythm Breakdown view for you to review and discuss. If you then choose to Accept them, new Epics/Defects are created in Rhythm with clear traceability back to the original external asset. This link provides a mechanism for feedback to the original author.
Each Project in Rhythm can contain a single Input Stream for Requirements and a single Input Stream for Defects. After an administrator sets up the Input Stream for the Project, you actively Accept or Reject each item that you want to add to the Backlog.
For Requirements, you need to create a filter in Atlas that contains all of the conditions that you want. When you do this, a query is created in Rhythm that you can set for the project. For example, you could create an Atlas Filter with the criteria Where Status = Planned. This query would pull all Requirements that meet the Filter condition.
The following columns are visible in the Requirements Input Stream grid: ID, Name, Type, Hub Priority, Priority, and Status. Only the Name and Priority properties map into a Story.
For Defects, an administrator can select any of the pre-existing queries that are defined in the Atlas Hub, or use default queries provided by Rhythm: All Items, All Open, All Open and High Severity, All Open in the last year, Flagged Items, Not a Priority, Priority, Status = Closed, Deferred, Open, Resolved, or Verified, Type = Defect or Suggestion, or Unread Changes.
The following columns are visible in the Defects Input Stream grid: ID, Name, Priority , Status, and Severity. Only the Name field is used when imported into Rhythm.
Project administrators enable this functionality in Admin Tools and can switch the query at any time during the project. After they have been configured, click Input Streams on the view to Accept/Reject individual items.
Whether an item appears in an Input Stream depends on the Query as well as it's internal Stream State:
Although you don't modify these directly, you can see the values when you compare versions of the original Input Stream asset on which the Story is based. And, there is a way to move a Rejected item back to Pending. See Rejecting an Item in Accepting Input Stream Items.