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
Top groups
Explore all groups
Community resources
Learn
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

Devil's advocate wanted: Disadvantages of moving documentation to Confluence + Jira

Eileen Palsson
Eileen Palsson Jan 28, 2019

Last week I asked a question:

https://community.atlassian.com/t5/Confluence-questions/Can-I-use-Confluence-for-creating-tech-docs-AND-for-tracking/qaq-p/988682

After getting a lot more info (not just on this forum), I believe that this move may be the way forward for our company. Our current docs (Word to PDF) and system of tracking them (Excel spreadsheet and associated Word documents - OMG) are from the Stone Age.  

But I also want to know some of the disadvantages of moving them to Confluence and Jira – for surely there are some. Please comment with problems you've had (or can foresee).

Thank you.

Comment
Watch
Like Be the first to like this
469 views

0 comments

Comment

Log in or Sign up to comment
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

See all events