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

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
4,465,932
Community Members
 
Community Events
176
Community Groups

Struggling with case-sensitivity between terms and acronyms

We're trying out this plugin, which is great, except that many of our acronyms can be common words (example: "Controller Area Network" with the acronym "CAN").  We don't have many mentions of "CAN" in all-caps, but we of course have lots of instances of "can", and we don't want those highlighted.

But we don't want to turn on case-sensitivity globally, because our documentation doesn't necessarily use titlecase for "Controller Area Network" or other terms.  Ideally we want:

- all our acronyms to be case-sensitive

- all our terms to be case-insensitive

The Smart Terms plugin doesn't seem to have any granularity for case-sensitivity, so how are other teams working around this?

1 comment

Hey @Rego Sen 

Unfortunately, this feature is still not available.
You can suggest a new feature to our dev team via this link: https://creativas.atlassian.net/servicedesk/customer/portal/4

You can also check our doc and YouTube mini-tutorials to know more about Smart Terms. 
Cheers

Khawla

Thanks for the suggestions.  Looks like I have to create a separate login for the feature ticket than this community one?  I now have 3 different logins for Atlassian stuff.  Is that something your team is looking into consolidating?

Hey @Rego Sen 

Sorry for the late reply!

No need to create another account; you just need to put your email ID!  

Here is the direct link: 

 https://creativas.atlassian.net/servicedesk/customer/portal/1/user/login?destination=portal%2F1

Regards

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events