What is project in Jira? Does it correspond to an application or a change

Question

So far we've used Jira projects as domains for more than 300 hundred from one-liner code runner applications to huge web applications. And whenever we have a task to work on a specific application, an issue is created under the corresponding project. But we often have situations that involve touching many applications. Let's say we have a requirement to provide customers with online chat service. That is going to involve making changes to 4 services and 2 web applications. How do we manage that in Jira?

1. If we create a project named something like "Online chat" how do we relate different tasks to their corresponding applications? In the future, if we want to see what changes have been made to an application X, how are we going to see it?

2. If we take one application as one project, then how are we going to group those projects under one project?

So, neither way seems to fit our needs. Do you have any suggestions on how to do that?

Scott Theus · Accepted Answer

Hi @mikayil-abdullah,

I currently use Components to set up projects that cross applications or platforms. Here's an example:

* Project; Update Data Storage to a Cloud based system
* Components: Application 1, Application 2, Database 1, Network update (and so on)
* Entities: Data Conversion, Script modification, Server Upgrade, Internet access Upgrade (etc.)
* Stories for each entity

Depending on how the project would be deployed I may also add Releases to the list of deliverables and assign the stories to both the components and the releases.

You can have multiple Components and Releases in a sprint and track them via custom filters on dashboards,

I hope this helps,

-Scott

Joe Pitt · Accepted Answer

I think of projects as a logical collection of related issues.  In your case of online chat you could use one project with a select or multi-select list of the applications they want chat enabled in if one person can set them up in all applications. If a different person needs to enable them in each application you could still use one issue and keep changing the assignee until all the work is done. Or it may make more sense to have a chat request issue in each application's project. It depends on how your internal structure works.

On 2. you can't group projects under another project.