I'm trying to find a way to archive old issues from one Section to another. So I have an issue tracker, with all my issues nested under this page. When I create a PDF export, i'd like the export to only include open issues, so my short term solution is to move closed issues to an archive page. Is there any method I can use to automate this, perhaps a macro?
So yes, it's a page nested under another page. It uses page properties to track status and other information.
I've got a page properties report on the main page, to track open issues with the label I specified in my template.
When I create a PDF export of my issue tracker and the contents below it, I don't want the export to include closed issues. So the easiest solution to that problem is moving closed issues to the archived page, but i'm trying to make this as simple as possible for end users.
That's understandable. It's a bit outside of what Confluence was made for, but JIRA didn't have the cross function to Confluence I was hoping for. Most of the issue trackers are document based to build new processes, T/S articles, etc.. So confluence makes more sense to use. I'll probably end up using a hidden page properties with a set of instructions how to archive the case for end users.
I've done something similar and build my reports using labels so it's just a matter of removing the label. Of course the label has to be added at the outset which we do by copying a 'template' page.
I think editing labels is easier than moving pages for a typical user.
Hello Community, Jessica here from the Confluence product marketing team! Today I wanted to get your takes on project planning –– what works, what doesn’t, how do you know if you’re doing it r...
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