Unknown macro: {bgcolor}

Unknown macro: {align}

Powered by Open Sources Licences from
[Adaptavist Theme Builder, Atlassian Jira, Atlassian Confluence, GreenHopper Plugin, Yourkit Java Profiler]

New architecture

Since last October, we are refactoring the Miżuri to turn it into a synchronization platform open to any repository where connectors can be created and extended freely.
Another significant change is the data model, which will now be based in a plain XML file and will not require any additional configuration in target repositories.
We expect these changes to be stabilized in the first quarter of 2011.
Until then, the latest stable version of the Mizura can be downloaded here.

Introduction

Welcome to Mizura.

Mizura provides a seamless integration between Atlassian Jira and Sparxsystems Enterprise Architect, keeping synchronized project issues and UML artifacts, like use usecases, requirements, activities and so.

Furthermore, a special MDA module provides a great OSWorkflow support, enabling a visual definition of worfklows for Atlassian Jira environments using the famous Enterprise Architect CASE.

Learn more

With Mizura, you can automate and synchronize project management tasks with your UML models, enabling agile teams to really implement the concept of "points" or "stories". In another words, with Mizura, you can create an usecase (or requirement, or activities, or... anything!) in a Enterprise Architect and, them, automatically create - and always keep synchronized - the related issue in Jira, or vice versa. Using this approach, your usecases/requirements/so can be showed in kanban charts or priorized

Mizura works in a bidirectional way, creating issues from UML elements, or creating UML elements from issues. In anycase, the full synchronization is enabled.

Nor only issues can be synchronized in Jira, but also Jira components and versions. See table bellow:

Table 1: Jira and Enterprise Architect synchronization support.

Enterprise Architect element	Jira element	Synchronization enabled?	Bidirectional?
Usecase	Issue
Requirement	Issue
Activity	Issue
Package	Component
Element link	Issue link

Package support under analysis, since Jira SOAP API does not have good support for it.

Architecture

Mizura is formed by 5 modules:

Module	Description
EA Connector	A wrapper to access Enterprise Architect repositories (.EAP files). It can be deployed has a standalone connector (i.e. for a single user usage) or in a Java EE container (i.e. ina multiuser environment). The connector interact with one or more repositories at once, reading and writing information in the models.
Jira Connector	A wrapper to access Atlassian Jira servers using HTTP protocol (SOAP approach). The wrapper can be deployed has a standalone connector (i.e. for a single user usage) or in a Java EE container (i.e. in a multiuser environment) The conector interact with one or more Jira servers at once, reading and writing information in the projects.
Mapper	A property file (in a future version could be a visual tool with a database store) to configure relations between Jira and UML elements. In the mapper, you can define things like "the usecase name is mapped to a issue summary", "the issue fixversion attribute is mapped to a requirement version attribute", "the usecase status is mapped to a issue status", "the package name is mapped to a jira component name", and so. In the mapper, you can define another settings, link synchronization periods, permissions, directions, exclusions, inclusions, and so.
MDA Connector	Enables the visual design of the Jira's worfklows using Enterprise Architect diagrams. This module is an Model Driven Architecture (MDA) transformation cartridge designed to work specifically with Enterprise Architect. This cartridge interpret EA Statuses and Activities diagrams converting them to the Jira workflows in the OSWorkflow format. With it, you can easily desgin Jira workflows in a powerful tool, applying them into multiple scenarios.
Spreadsheet Connector	Enables issues and UML artifacts be visualized like lines in spreadsheets (at first moment in Excel and GoogleDocs). The main objective is allow a quickly effort estimation of the project, since in our software proccess (3PUP), the first and second phases are dedicated to the baseline project estimation. So, initially, the analystis can fill some lines in pre-configured spreadsheets and then, import and always keep synchronized these lines with Jira and Enterprise Architect. In our case, these lines represents "the features" in FDD or "the user stories" in Extreme Programming or "the points" in Scrum.

Current status and Future works

At this moment, Jan/2010, the Mizura project was launched. We expect that a first functional release will be available in second quarter of this year, with an Open Source and Commercial licences. A final version came avaible in a fourth quarter.

Until then, follow the blogs and latest releases in the project source code repository.

Management

Latest management messages

*Debug Mode Activated:* Listing current macro parameters: * Param type: comment * Param ds: jiraDS * Param Key: MZ * Param like: $paramlike * Param trail: 3 * Param debug: false

Latest worklog activities

*Debug Mode Activated:* Listing current macro parameters: * Param type: worklog * Param ds: jiraDS * Param Key: MZ * Param like: $paramlike * Param trail: 3 * Param debug: false

Code

Latest builds (include Javadoc API and downloads)

Não foi possível recuperar http://3layer.com.br/bamboo/rss/createAllBuildsRssFeed.action?feedType=rssAll&buildKey=MZ-TRUNK - Página não encontrada.

Unknown macro: {html}

Árvore de páginas

Mizura Home