Best Practices

JFrog Security Documentation

JFrog Xray
Content Type
User Guide

Creating effective and manageable tickets in Jira or any issue-tracking system is crucial for maintaining an efficient workflow, clear communication, and project management.

A few strategies curated by Atlassian around organizing Projects are as follows,

  • Releasable product: Organizing your projects by releasable products or groups of work that share a common release cycle.

  • Team-based projects are another common organizational model. This allows your work to mirror your social organization and is convenient in less cross-functional setups, as it allows for more straightforward project permission management.

  • Business Unit: Closely related to organizing around teams, you might also consider organizing around larger business units - marketing, product, IX, IT, etc. Types of work will likely fall into similar patterns, making setting up workflows - and issue types particularly - more convenient.

  • Components: Be aware that using components, you can still sub-categorize issues within a given project.

We have seen our clients mix these strategies to have a solution that reflects their operational model.

Releasable Product

Your Jira will have a Project representing a “Product”. This project will be used to track all activities for the product. 

When creating a releasable product, various teams within the same group will work together to produce the final artifact. For instance, the engineering team will develop the core product while the dev ops team will create artifacts for log shipping, deployment, and other related tasks. Additionally, the database team will provide utilities for initializing and migrating the database.