Now that we have seen all the key aspects that make up a project, let's revisit what we have learned so far and put them to practice. In this exercise, we will be setting up a project for our support teams:
Let's start by creating a project category. We will create a category for all of our internal support teams and their respective support JIRA projects.
Please note that this step is optional, as JIRA does not require any project to belong to a project category:
Now that we have a project category created, let's create a project for our help desk support team. To create a new project, perform the following steps:
Support Desk – Global
, and accept the other default values for Key and Project Lead.You should now be taken to the Project Administration interface of your new project.
Having your project created, you need to assign the new project to your project category, and you can do this directly from the Project Administration interface:
As discussed in the earlier sections, components are subsections of a project. This makes logical sense for a software development project, where each component will represent a software deliverable module. For other types of project, components may first appear useless or inappropriate.
It is true that components are not for every type of projects out there, and this is the reason why you are not required to have them by default. Just like everything else in JIRA, all the features come from how you can best map them to your business needs.
The power of component is more than just a flag field for an issue. For example, let's imagine that the company you are working for has a range of systems that need to be supported. These may range from phone systems and desktop computers to other business applications. Let's also assume that our support team needs to support all of the systems. Now, that is a lot of systems to support. To help manage and delegate, we will create a component for each of the systems the help desk team supports. We will also assign a lead for each of the components. This setup allows us to establish a structure where the Help Desk project is led by the support team lead, and each component is led by their respective system expert (who may or may not be the same as the team lead). As we will see in the later chapters, this allows for a very flexible management process when we start wiring in other JIRA features, such as notification schemes:
Support Desk – Global
project.Internal Phone System
for the new component's name.admin
as the component lead.As we discussed earlier, while versions are most applicable for projects with deliverables, they can still be helpful for tracking and reporting purposes. For our Support Desk project, we can use versions to represent different calendar months, and each ticket or incident raised by users will have a version number attached. This way, it will be very easy for the management to pull up a report to see how many issues are being raised for any given month:
August
for Version Name.Now that you have fully prepared your project, let's see how everything comes together by creating an issue. If everything is done correctly, you should see a dialog box similar to the next screenshot, where you can choose your new project to create the issue in, and also the new components and versions should be available for selection too:
We will be exploring issues in more details in the next chapter.
If everything goes well, the issue will be created in the new project.