Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,458,239
Community Members
 
Community Events
176
Community Groups

Issue content not updated when navigating to another issue

Marie Skoldenborg
Marie Skoldenborg Dec 04, 2020

Scenario: 

Applications: Jira software and Jira servicedesk

I have opened one issue from the dashboard. The issue is linked to another issue. Pressing the link to open the linked issue: The issue id is updated in the navigation path, BUT the content is still the content of the previous issue. Workaround: Press refresh in Chrome and the content of the correct issue is fetched. 

The same sometimes goes for navigating from one issue to another by simply updating the issue id in the navigation address (Chrome). The content is not always updated when pressing enter. 

The same goes for me and at least one other user in my company. 

Is this a bug, or do we need to adjust some setting to make this work?

This problem was discovered about one week ago (late November). 

Answer
Watch
Like Be the first to like this
127 views

0 answers

Suggest an answer

Log in or Sign up to answer
Sourcetree
Sourcetree
TAGS

Atlassian Community Events

See all events