Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

I wanted to have a Document Management System with Rev Control as part of Jira

.One thing what i See is we currently use Confluence to store the Documents..Whenever there is a Change required..we go to Jira to create a issue an run through a Workflow..This seems Little bit Difficult and also the Rev sometimes is released before approval in Confluence.

One thing i saw is we have Components in Jira..I am hving an idea to Do that way,so that all issues in the Components with have issue traceability..Still there is No Control on Confluence yet..

Can Anyone propose a Better way.

1 answer

1 vote

Jira is an issue tracker, not a document management system, it expects to be paired up with a documentation system, not do it itself.  I'm not aware of any apps that would provide such a system within Jira.

The natural paired documentation system is Confluence, but that is not a document repository, it is a wiki.  Your documents are not lumps of data that you have to open in viewers or other programs, they're instantly available as web pages.

Conflluence pages have revision control.  It's simple, but there is a full revision history, it's one of the thinks a wiki does.

I would want to take a step back and look at how you are doing things and look at how you would like to be working.  Then evaluate a Jira/Confluence pair against what you want to be doing.  If it really is siloed working on monolithic docs, then you might be better served by getting a document repository system like Sharepoint.  If you want an open, collaborative and instantly updated set of docs, then maybe Jira/Confluence is the right way.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Asked in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

418 views 24 14
View question

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you