Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Satisfying External Auditor requests for software deployment using JIRA Edited

We at a least annually get an audit requests such as the following:

  1. Provide a system-generated listing of {insert major application here} code changes deployed to the production information system since {insert date here}.
  2. Provide a system-generated listing of {insert major application here} database changes deployed to the production information system since {insert date here}.

We have some thoughts on how to accomplish this but I wanted to get the community's  thoughts as well regarding transitions, hooks back from GitLab to Jira, Jira Workflows, etc. to satisfy these audit requests.

 

1 answer

It depends on whether your deployments are automated or manual, but you can accommodate both I think.   Normally I don't suggest a lot of customized Issue Types, but in this case it may be warranted for ease of auditing and clarity.  Something like:

  • Create a Software Release issue type and add whatever fields are needed for auditing.  Try to limit custom fields if the description will do.  Maybe just
    • Select list of Deployment Environments
    • Select list of Products 
    • ??
  • For manual releases you can create a Software Release issue and populate as needed.
  • For automated pipelines, you can have a standard/templated deployment action or step that creates an issue in Jira (push model).  You'd have to think about how to permission that.

One downside is that it won't scale nicely if your app consists of microservices or a lot of tiny bits.  You also probably don't want to execute this for lower environments.  "Hey , I pushed the shipping calculator service to QA for the 80th time today!"

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you