Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


Two boards with various tasks but no connection between

My group is set up with two boards. The first board is used by a few people and contains all the issues that our team is working on. The second board is used by a smaller team, and they use it to direct their workflow. Here is the issue: to set up a task on the second board, the team will LINK the task from the first board, manually copy and paste all the information they need, and then work from that new issue (on the second board). The problem is when the issue is updated with new information on the first board - there is no synch between the items on the different boards. Thus, the info isn't alway relayed to the team who is doing the work, and its not timely to rely on emails (heads down, don't always check emails). Is there a way to connect the two issues so that what is updated in the first board will be automatically updated in the second board? Is there a better way to create the issues on the second board? TIA 

2 answers

0 votes
Katarzyna Szumilas_Deviniti_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Oct 18, 2023 • edited

Hi @Allison Reece

Do you consider using 3rd party apps?
The problem you have described seems to be easily solved by synchronization apps. The one developed by my team, Issue Sync Pro lets you automatically create an issue in Project B when another issue is created in Project A.
By copying over issue data as fields, comments, attachments, and statuses, it keeps your two issues synchronized, making sure that important updates are automatically relayed to the team on the second board. It eliminates the need for manual data duplication and allows both teams to work with real-time, accurate information.

If that sounds like a solution you are looking for, feel free to test the app by yourself or book a free demo session with our team via this link.

Best regards,
Kasia from Deviniti

Thank you so much! The 3rd party app sounds interesting. I will use the link if there is interest to go 3rd party. 

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 18, 2023

Hi @Allison Reece -- Welcome to the Atlassian Community!

First thing, is this a single issue (work item) that just happens to display on two boards, and so it is copied...or is it two different work items for different teams?

  1. If it is one work item, have you considered using one issue, and allowing the board filters to display it on both?
  2. If it is two work items, how do you distinguish what work each team does with the common information on the issue?

Also if two items needing a sync: please determine which one is "the source", and then you could use an automation rule to update the fields of the other issue.

Kind regards,

Thank you!


It is a single work item, with each team doing various aspects of the work. My team has their own board, with all the copied tasks/issues, to direct their workflow. I didnt realize each team could use filters to only display the info that is pertinent to them. If they did this, would they get all the updates regardless of where they are added? The problem is missing information that comes in late. 

Thank you!

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 19, 2023

Hmmm...You noted a couple of interesting things to me:

  • Each team has various aspects of the work
  • Each team needs visibility to any common information updates

That makes me wonder if using an Epic to contain the common information would solve both needs, as the child issue for each team could be created, be worked individually on their own board, and when both are completed the Epic could be moved to done.

This is a great answer, thank you. I am very new to Jira (week 2), so I will need to ask some questions to find out why it was set up as it is. But, an Epic sounds like it would do what we need. Thank you!

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events