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

Comments on issues moved from JWM to JSM become public

Dirk Ronsmans
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 31, 2023

This might seem a bit of an odd one but I'm wondering if someone has a fix for it or a different train of thought.

I currently have several issues in JWM that are being worked on and for reasons need to be moved to a JSM project.

That in itself is no problem, just "move" the issue and map it to the new project.

However, all the comments on the JWM issue become public comments on the JSM issue. (they won't be seen on the portal until I set a request type) but having the default set to public seems a bit weird.

Is there any way to make the comments "internal note" by default when moving between products? This is pretty much a JSM only issue as JSW and JWM don't have the distinction between the two.

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events