Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,558,367
Community Members
 
Community Events
184
Community Groups

Testing Artifacts on Jira Issues - what is best practice for where to post and store these?

Hi all, 

I'm interested in learning best practices for making QA Testing Artifacts immediately visible with dates that they're added, with who is adding the Testing Artifact, with a description. 

We currently have QA Testing subtasks on our Issues.  We have a Test Results custom field.  Some of our testers are adding QA Testing Artifacts as a Comment on the Issue (yields the most benefit as it shows who, what, when).  Some testers are adding attachments to the QA Testing Sub-task.  Some testers are adding pictures or text to the custom Test Results field we have in the Issue (can't tell who or when with this).  

What is best practice?  

Thank you. 

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events