Jira as a data catalog

Question

My work is wanting to use Jira as a data catalog, I.e, this query was written by so and so, which is used in this stored procedure, created on this server, and created on this database on said server, which connects to this server and database,to produce this report, which is used in this SSIS package, which is executed by this Job on server so and so. By the way, the data steward of the report is this person, and the POC for the report is this person who manages this account, and when an error occurs contact developer so and so.  Is this probable, a reality, etc.

Thank you,

Carlos Garcia Navarro · Answer

Thanks for the details. For more context, why don't you use the data source (the DB) as your data catalogue. If a DB field maps to a Jira issue how much information is there in the DB field, and what information do you want to track in the Jira ticket?

Ruben Alliet · Answer

Hi,

So we were thinking about the following:

- Each DB field or table from our Data sources(MSSQL & Bigquery) would be a Jira issue and those would be linked together with relationships. Those Jira issues would contain information about the field/table like Data owner,Data steward,sensitive data yes/no,Identity and access management rules.

the relationship would kinda look like this:

FIELD

/

Table -    FIELD

\

FIELD

- Those field names and table names (originating from MSSQL & Bigquery) should be synchronized with the JIRA system and create/update jira issues using A) the JIRA API or B)  a direct connection with the JIRA DB

Please let me know what your opinion is about the following?

Carlos Garcia Navarro · Answer

Hi @Ruben Alliet , can you describe your use case? Then I can tell you how I think Jira could be used to cover your case. Thanks :-)