In Agile board where can I track external dependencies

[CindrellaR]

As part of integration, I have dependencies on a Access Management tool readiness, Where do I track dependencies in a Agile board?

[GlideFather]

Hi @CindrellaR,

please provide more details on what dependencies are we talking about. 

The data from Agile board are stored in multiple tables (usually starting with "rm_" prefix) and they are then referenced.

So please specify what exactly would you like to know, this is too vague to answer...

However the Agile tables, roles, and properties can be found here: 

• Components installed with Agile Development 2.0 
• Agile Development process data model 
• Agile board in Agile Development 2.0

Tables installed

Table Description

Product Assignment Group [m2m_product_group]	Stores relationship between products and groups.
Release Assignment Group [m2m_release_group]	Stores relationship between releases and groups.
Application Model [cmdb_application_product_model]	Represents whole product whose releases are being managed.
Release Product [m2m_product_release]	Represents all managed products.
Story Dependencies [m2m_story_dependencies]	Represents all related stories (prerequisite and dependent) to an existing story.
Scrum task [rm_scrum_task]	Represents a discrete amount of work for a story carried out during a sprint.
Release team member [scrum_pp_release_team_member]	Represents the list of users who are part of a release.
Sprint team member [scrum_pp_sprint_team_member]	Represents the list of users who are part of a sprint.
Team [scrum_pp_team]	Represents who completes scrum tasks and stories during releases and sprints.
Team name [scrum_pp_team_name]	Represents the name of the scrum team.
Theme [scrum_theme]	Represents either a tangible product (such as a trading application) or an abstract goal (such as performance tuning).
Scrum release [rm_release_scrum]	Represents individual versions (releases) of the product. Each release contains a list of sprints with a time range in which the stories in those sprints must be completed.
Sprint [rm_sprint]	Stores sprints, which are the backlog items to be addressed together during a given time period.
Epic [rm_epic]	Represents related stories or requirements that you have not yet transformed into stories.
Story [rm_story]	Represents self-contained pieces of work that can be completed within a sprint.
Defect [rm_defect]	Represents a deviation from the expected behavior of a product.
Documentation Task [rm_doc]	Represents documentation tasks for the product.
Enhancement [rm_enhancement]	Represents an improvement to an existing product.
SDLC release [rm_release_sdlc]	Represents individual versions of the product.
Testing Task [rm_test]	Represents testing tasks for the product.

[GlideFather]

Hi @CindrellaR,

could you provide any feedback - solved or still something's needed?