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.

×
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

Can't see issues in Jira Structure when Automation is off

Hi,

I am running into a weird problem. My team uses a Jira Structure to manage and track our work. Within one of the folders we have a few Milestone tickets. The problem is, some team members can see all Milestone tickets just fine; but some can't see all Milestone tickets within folders if Automation is not turned on for them.

Specifically, Milestones which don't have Initiatives, Epics, etc linked to them are not visible for some team members, they can only see Milestones which have Initiatives, Epics, etc. To see Milestones without linked tickets, they have to turn on Automation. Interestingly, this problem is faced only by some team members; and for others, all Milestone tickets are visible irrespective of whether Automation is turned on/off or whether those Milestones have linked tickets or not.

Any solutions to this??

1 answer

1 vote
David Niro
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 16, 2023

Hello @Ripudaman Singh Kushwah ,

Welcome to the Community!

Initially, this sounds more like some inconsistency between the users' project or structure permissions.

I would start by reviewing which Groups the users from both subsets belong to and if there may be differences in the project and structure permissions.

It would also be beneficial to check which browser the users are accessing structure from and if they experience the issue from a different browser or in incognito mode.

Please feel free to contact our support team directly via support@almworks.com or through our customer portal support.almworks.com.  We will be happy to help you troubleshoot the issue and identify the cause.

Best,
David

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events