But I noticed the following: When you have a Story ticket (which appears in the sprint board and backlog views) and convert it into an Epic (using the "Move" function), then magically the ticket still appears in the sprint board, now as an Epic. Weird thing is, that when you search for it on the Backlog view, it does appear as an Epic in the

I'm fairly new the to automation within Jira. I have two questions. If a bug is created in a Jira project and in the description field there is, for example, the text {KIM1} Since KIM1 is already created as a component in the project is it then possible to automatic add KIM1 as a component to the bug and if yes. How is this done most correctly?

1 - Use a template. When starting a new Jira ticket, developers might get a form of writer’s block. Even after creating a ticket, necessary information may be missing. By using a checklist template (like the one below) you can avoid this problem. Here is a template in markdown I use to create scope for new Jira tickets:
Flow that works: Go to "Backlog". Locate a ticket. Drag&Drop to "Board" section or click "Move to Board" in the "" menu at the right. Flow that does not work: Go to "Issues". Search for a particular ticket and open it. Change status from whatever to "In Progress". Go to Filters->Advanced Issue Search. From there, you can select Epics under Issue Type. Select a project or projects to limit those. You can choose what information to display by selecting the fields you want in the Columns dropdown. Finally, click on Export, to extract the table into a variety of formats, including CSV.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
If the Epics panel is not shown at the left of the screen, select Tools > Show Epic Panel. In the Epics panel, click the triangle at the left of the epic name to display the epic details. Drag the issue (s) onto the relevant epic. The epic will turn green (see Screenshot 2 ). The epic's name will be displayed on the issue as a coloured lozenge. Configure progress % calculation on either "remaining estimate" or "original estimates". Epic Tree directly on Issue Screen. Display and manage Epics/Issues of your project. Real time edit option for Issue summary, status, time estimates, story points and assignee on the tree on the Epic Hierarchy. Rolled up percentage completion and at issue Internally, we call our initiatives “PC Tickets.” Project Central tickets are configured in Jira Software just like our epics. Each team takes their four or five most important goals for the year and makes PC tickets for each one. These PC tickets are used by the founders and management to understand all the work being done in the company. vt0cpV.
  • bd193gqfww.pages.dev/891
  • bd193gqfww.pages.dev/768
  • bd193gqfww.pages.dev/250
  • bd193gqfww.pages.dev/384
  • bd193gqfww.pages.dev/724
  • bd193gqfww.pages.dev/453
  • bd193gqfww.pages.dev/168
  • bd193gqfww.pages.dev/923
  • bd193gqfww.pages.dev/375
  • bd193gqfww.pages.dev/745
  • bd193gqfww.pages.dev/433
  • bd193gqfww.pages.dev/854
  • bd193gqfww.pages.dev/819
  • bd193gqfww.pages.dev/391
  • bd193gqfww.pages.dev/530

    • jira convert ticket to epic