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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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

Sprint board layout - can the same ticket be visible on two seperate persons board

When we have a ticket for development, the normal process is that a developer will do the development then they will re-assign the ticket to QA for testing....its at this stage that the ticket becomes lost in the sprint to the developer as it now sits with the assigned QA (lots of tickets). it is only when the QA has assigned it back to the Dev that they see it again (apart from manually going to QA column and searching). 

I noticed there is a 'Original dev assignee' aswell as 'assignee field'.....i tried testing if i use the the QA as the assignee and the Original dev assignee stayed as the dev would the ticket appear on the sprint board under QA column for both but it does not.


I would feel maybe this would cause a double up on ticket numbers? I know the dev could search for their ticket via a filtered view however i wanted to enquire if there was a work around for both QA/Dev to be able sight the ticket within the same sprint board as it works its way through the sprint board.


Screen Shot 2023-05-08 at 2.44.22 pm.png


1 answer

2 votes
Walter Buggenhout _ACA IT_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 08, 2023

Hi @Gary McDermott,

Which issues are visible on a board is determined by the board filter (configurable via Board Settings > General in company managed projects). From what you describe, it seems as if you have boards set up for individual users, as you seem to be retrieving issues by the assignee field.

It is more common practice to set up a board for a team, rather than an individual user. If you do not restrict your issues per assignee, they automatically become visible for all members of the same team, which better serves the purpose of collaboration.

Hope this helps! 

Suggest an answer

Log in or Sign up to answer