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,125
Community Members
 
Community Events
184
Community Groups

Testrail and JIRA subtask interaction

We are using JIRA and have Testrail integration enabled. 

Our current implementation does not use "sprint bugs" (subtasks on the stories), but rather only issuetype = bugs.  I've been told this is because Testrail cannot handle subtasks.  I've done some light reading here but I haven't found a definitive answer.  I'd like confirmation that Testrail does not handle subtasks on JIRA stories. 

1 answer

I've found a partial answer. 

http://docs.gurock.com/testrail-integration/tools-jira-fields

(Yes, it's overall possible.) 

However, the question in the following post makes me wonder if there's a negative impact on Testrail reporting.

https://discuss.gurock.com/t/assigning-defects-as-sub-tasks-in-jira/6152/7  

So it would still be great if someone more knowledgeable weighed in. 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events