JIRA is the workflow tool used by oneMarketing. It helps organize all processes around software development.
All processes in oneMarketing software development are modeled in JIRA. These include:
By using this one tool, it can be assured that all requirements regarding oneMarketing are collected centrally and therefore won’t be forgotten.
Access to JIRA is limited.
In a standard set-up, JIRA is used to organize work packages. It is not meant to be used for documentation purposes.
JIRA is used to organize work packages, and is not intended for documentation purposes. Each ticket is assigned different statuses while the corresponding issue is being worked on. Examples include "Open", "In Progress", "In Quality Assurance" and "Done". The tickets are also assigned to different team members and stakeholders over the course of the project. Anyone assigned to a ticket is automatically notified once the ticket is updated.
It is of utmost importance that every member of a project team follows the same rules of treating tickets and changing the respective status. During the starting phase of a project, you should align on a modus operandi and communicate that to every stakeholder.
JIRA is closely related to CONFLUENCE. The technical integration integration ensures that the respective issue is related to an article in CONFLUENCE and vice versa.
The Allianz Jira can be found here
https://jira.collaboration.allianz.io/
You will receive different URLs from your project manager or someone in a similar role depending on the project you're working on. This link will open a blank start page if you are not a member of a project.
CONFLUENCE is the documentation tool used by oneMarketing. Similar to social media tools, it is collaborative and can be read and edited by various persons.
CONFLUENCE is meant to be the go-to documentation source of your project. Anything you need to document should be kept here in a clearly structured way. Members of a team are supposed to keep the content up to date in a collaborative way: whoever has the best knowledge of a topic should provide the respective content. Thus, a feature is described from the first basic idea until the final documentation.
In CONFLUENCE you can
CONFLUENCE is closely related to JIRA. The technical integration makes integration ensures that the respective, the respective article is related to an issue in JIRA and vice versa. This allows to always display the current development status in a CONFLUENCE article. To make use of this integration and relate the organizational part with the documentation, insert the respective JIRA macro into a CONFLUENCE article.
Access Confluence at:
https://jira.collaboration.allianz.io
You will receive different URLs from your project manager or someone in a similar role depending on the project you're working on. This link will open a blank start page if you are not a member of a project.
