Marketing can be a cyclical process. We marketers typically plan projects, assign work, review content, publish, and then…. start all over again. At the beginning of each quarter we approach this process with bright-eyed enthusiasm, big ideas, and a clear plan of attack. But as the months wear on, and more (or unexpected) work accumulates, it can be tough to manage projects and keep the process together.
That said, having the correct tools in place can alleviate the manual labor of staying organized and can sustain team momentum. On the JIRA Marketing team, we use JIRA Core and Confluence together to keep all our programs running smoothly. For those who need a refresher, JIRA Core is a task and project management solution for business teams, and Confluence is a tool for document sharing and content collaboration.
How exactly do we do this, you ask? Let’s take a look inside our process of writing and promoting a blog to see how our team drives work from to-do to done.
Planning: create a JIRA issue from inside Confluence
Before writing a blog, our team gets together to brainstorm content and produce a solid outline, which is done in Confluence. We create the promotional plan, record our notes, and then break it down into actionable items. For instance, these items could be: 1.) Write blog content, 2.) Collect blog images, and 3.) Send promotional email.
Having defined the work to be done, we then create these tasks in JIRA Core so we can properly track them through a workflow. In Confluence you can highlight the text and choose the Create JIRA issue option.Then, enter the project name, issue type and description. Your highlighted text will automatically populate within the issue summary field. Just like that, your tasks are recorded in JIRA Core. Check it out:
[WPGP gif_id=”34462″ width=”600″]
Working: add a shortcut for easy access
If Confluence is our tool for ideation, then JIRA Core is our main driver for tracking our activities. We can see where the task is in our workflow and evaluate our progress.
Continuing with our example, we open the first task (write blog content) and assign it to the appropriate person. Once that person begins writing they can set the status to “In Progress.” From here, we can communicate questions and feedback, and keep the issue moving to “In Review” and eventually “Done.”
While we track the issue in JIRA Core, the blog post is written in Confluence. To easily access this content in JIRA Core, we can add a shortcut link that connects to our Confluence page. To do this, simply go to the side bar in JIRA Core and add the shortcut link.
Get your issues in order
The blog copy isn’t the only issue being worked on. There are images that need to be created and added, and email templates that are being designed. For the most part, we view this information in JIRA Core. But, what if we want to see these tasks on the same Confluence page as our written blog? One easy way to see issues from within Confluence is to copy and paste each separate task URL directly to the page.
However, if you want to see more information than just the issue title, you can use the JIRA Issues Macro found in the content dropdown in the top navigation. What information you choose to see is completely customizable. Show the issue summary and assignee, or add the due date and status. Specify how many tasks are displayed and from which project. Get even more granularity by using JQL to filter and select an order. If you want to view tasks in order of due date, that’s possible, too.
Reporting: gain some perspective
We have many blogs being written simultaneously, so it’s nice to get a bird’s eye view of what topics are ahead. We do this in either JIRA Core or Confluence by pulling blog tasks into a calendar. In your JIRA dashboard there is a calendar gadget where you can see how many blog posts are coming out per week.
Or, see more details of each blog post by using the Team Calendar Macro in Confluence. Here you can choose specific projects to display and automatically pull the tasks into the calendar. Specify if the tasks are visible on their start date, due date, or span across both. And, if you change a date in JIRA, it will automatically update in the calendar.
Using JIRA and Confluence together has allowed us to maintain organization and maximize efficiency, for the sake of our collective team sanity. That bright-eyed, energetic, beginning of the quarter feeling? With the right tools in place, it can last all quarter long.
Want to try these integrations out for yourself? Get started in JIRA Core and Confluence.
Did you find this post useful? Share it on your social network of choice so your fellow Marketers can learn about project management in JIRA Core, too!