Labels in epic description

[Michał Bieńkowski]

I would like to create labes for my system keywords like e.g. PC-A, PC-B, PCBA etc, so I can have something like dictionary. With this I could easily refer to e.g. particular PC. Then with this labels I could write epic description like "<PC-A> shall do this and this. <PC-B> shall to something else." (where <> represents label). How to do it in Jira? In Todoist if you have a label you can easily access it just by use of @ character.

EDIT:

Perhaps my problem description is not clear enough, at least that's what I assumed based on the replays. What I really need is a dictionary - I just thought that labels could do the trick, but now I see it's wrong direction. In my opinion it is really hard to describe a requirement using only fields. Even if it's possible, it won't be readable and for sure everyone could interpret it in different way. 

The point is to define a dictionary in one place e.g. PC-A is a PC with serial number XXX, PC-B with s/n YYY. And then write description and reference this dictionary item (find on the list). The best would be something like this https://get.todoist.help/hc/en-us/articles/205195042-Labels but with one dictionary per project.

[Jacob Piotrowski]

Try organise your work with components:
https://support.atlassian.com/jira-software-cloud/docs/organize-work-with-components/

Combination of components and labels should be enough.

[Michał Bieńkowski]

Can I use components in description filed?

[Nic Brough -Adaptavist-]

Jira is not a free-form editor where you might usefully sprinkle your text with labels and other meta-data.

Each field has a purpose, and fields are more powerful than free-form text because they have a purpose. 

To label an issue, use the label field.

[Michał Bieńkowski]

Perhaps with fields I have the ability to search/filer easier, however IMO with only fields the description becomes unreadable. Label field would not fit.

[Rudy Holtkamp]

Hi @Michał Bieńkowski ,

Labels are used system wide. Which means that if you create a label in one project it will be available in every project.

With JQL (Jira Query Language) you can select all the issues you have labelled, e.g.

labels in ("PC-A", "PC-B) 

An epic can be used as umbrella and you can link all issues to it, However you can't use a JQL to link the issues to the epic. You need to do it manually. 

[Michał Bieńkowski]

Ok, so now I know that labels are not what I need. It can't be system wide.

[Adam Zaborski]

Maybe this give you the reverse/new look upon your needs - https://support.atlassian.com/jira-software-cloud/docs/search-for-issues-using-the-text-field/#Term-searches

BTW Michał Bieńkowski are you from 'Hydrozagadka' ? and SLASH ?