If I create a Product requirements page with individual requirements defined on that page, will these be version controlled from a point of sign off or from a point that I define? Or would I need to attach documents that would themselves be subject to version control as defined by Milo? I am trying to work out how to use Jira and Confluence in combination for requirements documentation and workflow (through review and sign off by business reps) but need versioning so that if our supplier cannot deliver the functionality to exactly met the requirement, any changes to the original requirments are taken forward as a version 2, 3, etc. with the original, signed off version retained.
No, it's versioned from the point of creation. Every time you edit a page, you get a new version. Attachments are versioned separately from the page, again, from the point of creation in Confluence. This is not so much "version control" as just plain versioning - every change has been tracked. I think what you're asking for is a bit more complex than this. I suspect you're looking for some form of authorisation and sign off stuff - I'd take a look at Comala Workflows and Scroll Versions - different approaches, but both really good at looking after publication type stuff.
Hi my Community friends! For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs