EXPORT EPICS/STORIES/ BUGS from Jira to Excel (.csv)

-

 

EXPORT EPICS/STORIES/ BUGS from Jira to Excel (.csv)

STEP - 1 :

Open the Jira tool

Click on Filters

Select Advanced issue Search as below


STEP - 2 :

Select the Project as shown below


STEP - 3 :

Click on Excel Button to download and open the issues in the excel as shown below


STEP - 4 :

Click on Excel on Desktop ( In the Trial Version )




 


STEP - 5 :

Final CSV Template Downloaded


 

Real Time

In the Real time Click on Jira for Excel App à To Add Add-on to Jira





  

EXPORT CSV File to Jira

You can extract the ideal CSV template directly from your own site. These would be the steps:

  1. If you still don't have any issues created, manually create a new issue in your Jira site. If you already have, jump to the next step
  2. At the top header of any Jira page, click in the Filters menu > Advanced issue search

In the new page, keep the filter bar empty and click enter. It will return all the issues created in your site

  1. Click in export > Export Excel CSV (all fields):


The file exported will have all the fields you currently have for your issues described in the first row, so you can simply delete the values from the next rows and use the header as a template. The only required fields to make the import works are Summary, Project Key, and Project Name, so it's okay If you want to keep some fields empty.






Comments

Post a Comment

Popular posts from this blog

What Does a SM-SCRUM MASTER do “All the Day”

-
What Does a SM-SCRUM MASTER do “All the Day” ·         Facilitate the Daily Scrum (Timeboxed) o    Facilitate the Daily scrum meetings for the team and maintaining the time box ·         Arrange the Follow-up meetings o    Arrange the follow-up meetings for the detailed discussion after the daily scrum meeting, if anything is raised in the daily scrum meeting ·         Meeting with the PO – PRODUCT OWNER o    To arrange the meeting with the PO to support the Backlog creation and the Road Map preparation ·         Facilitating the SCRUM EVENTS   o    such as – BACKLOG REFINEMENT, SPRINT PLANNING, SPRINT REVIEW AND SPRINT RETROSPECTIVE meetings. ·         Meetings with the Team’s Manager                     o  SM will have the meetings with the Team’s manager to discuss about the people’s issues, Trainings etc. ·         Contribute to Community of Practice o    SM with communicate with the other SM’S and contribute to the Agile community of practice in the company
Read more

When to choose scrum and when to choose kanban? Explained with examples

-
Scrum and Kanban are two popular frameworks used in Agile project management. The choice between Scrum and Kanban depends on the nature of the project and the team's preferences. Here are some examples of when to choose Scrum and when to choose Kanban: When to choose Scrum: 1. Complex projects with evolving requirements: Scrum is suitable when the requirements of a project are likely to change during the development process. It allows for flexibility and iterative development with regular feedback loops. Example: Developing a new software product where the requirements are not fully known initially. The Scrum framework enables the team to adapt to changing customer needs and deliver a more satisfactory product. 2. Projects that require rigorous planning and structured timelines: Scrum is beneficial when a project requires a strict timeline and frequent checkpoints for progress assessment. The framework provides a clear structure for planning and organizing work. Example: Building a
Read more

Kanban board setup for AMS teams in SAP

-
To set up a Kanban system for AMS teams in SAP, you can follow these steps: 1. Define the workflow: Understand the specific stages involved in the AMS (Application Management Services) process. This can include stages like ticket creation, assignment, analysis, development, testing, deployment, and closure. Determine the sequence and dependencies of these stages. 2. Create Kanban columns: Map each stage of the AMS process to a separate column on the Kanban board. For example, create columns like "To Do," "In Progress," "In Review," "Ready for Deployment," and "Completed." 3. Define work item types: Classify the types of work that the team will handle. This can include different types of tickets or tasks like bug fixes, enhancements, or system configurations. Assign a specific color or label to each work item type. 4. Set WIP limits: Establish work-in-progress (WIP) limits for each column to avoid bottlenecks and promote smooth flow. Def
Read more