Many organizations are using JIRA for issue tracking – incident, service request, problem and change management, as well as for project management. However, JIRA can also be used as a tool for test management.
Presentation was given on TAPOST 2012: http://www.itbaltic.com/en/conferences/tapost-2012/
JIRA is an issue tracking tool from Atlassian that allows users to prioritize, assign, track, report, and audit issues. It provides customizable reporting with detailed graphs and charts. Users can map their business processes with a custom workflow. JIRA integrates with other systems through an open API and over 100 free plugins. Issues are tracked in JIRA and have attributes like status, priority, assignee, comments. Workflows define the life cycle of an issue. JIRA can also be used for agile project management like Scrum, tracking user stories, sprints, and providing burn down charts.
Introduction to Jira - Bug Tracking toolGlobal SQA
JIRA is an issue tracking software that allows users to prioritize, assign, track, and report on issues. It provides customizable workflows and templates to track bugs, tickets, tasks and projects. Key features include easy issue creation, reporting, roadmaps, notifications and powerful searching. JIRA aims to improve productivity by streamlining issue tracking and ensure quality by recording all details until completion. It provides customizable workflows, templates and over 100 community plugins to extend functionality.
This document discusses using Jira software for test management. It provides an overview of Jira, describing it as an issue tracking and project management tool. It outlines Jira's pricing models and features for test management like creating test cases, executing tests across test cycles, and generating reports. The document also discusses using the Zephyr test management add-on with Jira to manage the full testing lifecycle within a single tool.
JIRA is an issue tracking tool that allows users to prioritize, assign, track, report on and audit issues. It is a customizable platform that can be used for software bugs, helpdesk tickets, user stories, change requests and other tasks. JIRA improves productivity by streamlining issue tracking and coordination, and improves quality by ensuring all tasks are fully documented and followed through to completion. It provides features like sub-tasks, versions, search capabilities, reporting, configuration options and workflows to support various use cases including service desks, project management, agile development and more.
JIRA is a project management and issue tracking tool used by agile teams. It allows users to prioritize, assign, track, and audit issues like software bugs, tasks, and change requests. Originally an issue tracker, JIRA now provides customizable workflows for tasks like requirements management and support ticketing. It is used by many large companies and offers plugins to extend its functionality.
Jira fundamentals and bug tracking tool GuideMayank Solanki
JIRA is a highly customizable issue tracking system that allows users to:
1. Track bugs, tasks, and other issues across multiple projects.
2. Customize workflows and integrate with other systems.
3. Use plugins to expand its capabilities for project management and tracking tasks, deadlines, and activity.
JIRA is an issue tracking tool used by over 25,000 customers for project management and issue tracking. It allows users to create issues, organize them into projects and prioritize them. Issues flow through different statuses as part of a workflow, from new to closed. Projects contain issues and are collections defined by an organization's needs, such as a software development project. Components and versions further help categorize issues.
The document provides an overview of JIRA concepts including projects, issues, statuses, resolutions, and priorities. A project contains a collection of issues and has a name and key. Issues represent bugs, epics, improvements, features, stories, and tasks. Statuses track an issue's stage from open to in progress, resolved, and closed. Resolutions indicate how an issue was addressed like fixed, won't fix, or duplicate. Priorities denote an issue's importance from blocker to critical, major, minor, and trivial.
The document provides an agenda for a presentation on JIRA. The agenda includes explaining what JIRA is, discussing JIRA concepts and features, explaining why JIRA is useful, demonstrating how to use JIRA live, and holding a question and answer session. Sections of the presentation will cover topics like what JIRA is used for, how issues, projects and subtasks are organized in JIRA, example implementations of JIRA in different contexts, and key features and benefits of the software.
Using JIRA & Greenhopper for Agile DevelopmentJeff Leyser
This document discusses using JIRA and Greenhopper for agile development. It provides an overview of JIRA as an issue tracking platform that can be used for various purposes including project management, help desk support, and software development. It also discusses Greenhopper, an agile project management plugin for JIRA that includes planning, task, and chart boards. The document concludes by encouraging evaluation of JIRA and Greenhopper.
Xray for JIRA is a test management plugin that allows users to manage both manual and automated tests inside JIRA. It enables specifying test cases and preconditions, organizing test cases using test sets or hierarchies, planning tests with test plans, and executing tests by creating test executions and test runs. Xray integrates with automated test frameworks and provides reporting and traceability between requirements, tests, test runs, and defects.
This document discusses Agile project management tools and methodologies. It covers JIRA Agile for tracking work in an Agile workflow, the Scrum framework, and its events and artifacts like sprints, product backlogs, and burn down charts. It also mentions the Agile manifesto and its values of prioritizing working software and customer collaboration over documentation and contracts.
Dan Chuparkoff is a group manager at Atlassian who uses JIRA. The document provides an introduction to using JIRA for agile planning, work tracking, and dashboards. It discusses challenges in defining and estimating tasks and using story points. It also contrasts Scrum and Kanban methods for organizing work in JIRA and explains plan and work modes.
Use of Jira Confluence as Project Management ToolJipin Nakarmi
This document provides an overview of the Jira and Confluence tools. It describes Jira as a customizable issue tracking system that can be used to manage projects, bugs, and software development. Confluence is described as an enterprise wiki for collaboration and knowledge sharing. The document outlines some of the key features of Jira, including workflows, dashboards, and the GreenHopper agile plugin. It also lists some potential uses for Confluence, like requirements gathering. Finally, it discusses benefits like more maintainable code, early bug detection, and better estimating through the use of these tools.
The document provides an agenda for a JIRA Agile workshop. It begins with an overview of Agile and Scrum principles and frameworks. It then discusses what JIRA is and some of its key concepts like issues, projects, tasks, and stories. The document outlines JIRA features, workflows, user management, and tools like reports, boards, dashboards, and time tracking. It distinguishes between story point and effort estimation. Finally, it leaves time for questions.
Jira is a project management tool released in 2002 by Atlassian that is widely used for managing products, projects, processes, and services. It was originally derived from the word "Godzilla" and was initially only available on-premise, but now has a cloud-based version called Jira Cloud. Jira provides configurable settings and plugins to customize development or project management workflows, and can integrate with other Atlassian tools to automate processes from start to finish.
In this quality assurance training, you will learn Defect Management tool - JIRA. Topics covered in this session are:
• What Exactly is JIRA?
• JIRA as an Issue Tracker
• JIRA as a Project Management Tool
• JIRA Roles
• JIRA Request Format
• JIRA Workflow Model
• General JIRA Structure
• Browsing Project issues
• Created vs Resolved issue Report
• JIRA Help
For more information, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-training-beginners-and-intermediate-level/
Jira software 8.0 8.5 community presentationMaitrey Patel
The document discusses the new features and improvements in versions 8.0 through 8.5 of Jira Software. Key highlights include a new Lucene search engine making Jira 20x faster, improved email notifications, priority icon updates, and the introduction of a mobile app. Upgrades from 7.0 to 8.0 include a customized pre-upgrade planning page. Feature releases like 8.1 add support for Java 11 and SQL Server 2017. The Jira 8.5 enterprise release will target Q4 2019 and include backported security updates.
The document provides an agenda for a presentation on JIRA. It will discuss what JIRA is, key concepts like projects and issues, features such as reporting and notifications, reasons to use JIRA, and include a live demonstration and Q&A. JIRA is an issue tracking tool that allows users to prioritize, assign, track, and report on issues. It is customizable and aims to improve productivity and quality.
AI Risk Management: ISO/IEC 42001, the EU AI Act, and ISO/IEC 23894PECB
As artificial intelligence continues to evolve, understanding the complexities and regulations regarding AI risk management is more crucial than ever.
Amongst others, the webinar covers:
• ISO/IEC 42001 standard, which provides guidelines for establishing, implementing, maintaining, and continually improving AI management systems within organizations
• insights into the European Union's landmark legislative proposal aimed at regulating AI
• framework and methodologies prescribed by ISO/IEC 23894 for identifying, assessing, and mitigating risks associated with AI systems
Presenters:
Miriama Podskubova - Attorney at Law
Miriama is a seasoned lawyer with over a decade of experience. She specializes in commercial law, focusing on transactions, venture capital investments, IT, digital law, and cybersecurity, areas she was drawn to through her legal practice. Alongside preparing contract and project documentation, she ensures the correct interpretation and application of European legal regulations in these fields. Beyond client projects, she frequently speaks at conferences on cybersecurity, online privacy protection, and the increasingly pertinent topic of AI regulation. As a registered advocate of Slovak bar, certified data privacy professional in the European Union (CIPP/e) and a member of the international association ELA, she helps both tech-focused startups and entrepreneurs, as well as international chains, to properly set up their business operations.
Callum Wright - Founder and Lead Consultant Founder and Lead Consultant
Callum Wright is a seasoned cybersecurity, privacy and AI governance expert. With over a decade of experience, he has dedicated his career to protecting digital assets, ensuring data privacy, and establishing ethical AI governance frameworks. His diverse background includes significant roles in security architecture, AI governance, risk consulting, and privacy management across various industries, thorough testing, and successful implementation, he has consistently delivered exceptional results.
Throughout his career, he has taken on multifaceted roles, from leading technical project management teams to owning solutions that drive operational excellence. His conscientious and proactive approach is unwavering, whether he is working independently or collaboratively within a team. His ability to connect with colleagues on a personal level underscores his commitment to fostering a harmonious and productive workplace environment.
Date: June 26, 2024
Tags: ISO/IEC 42001, Artificial Intelligence, EU AI Act, ISO/IEC 23894
-------------------------------------------------------------------------------
Find out more about ISO training and certification services
Training: ISO/IEC 42001 Artificial Intelligence Management System - EN | PECB
Webinars: https://pecb.com/webinars
Article: https://pecb.com/article
-------------------------------------------------------------------------------
Join educators from the US and worldwide at this year’s conference, themed “Strategies for Proficiency & Acquisition,” to learn from top experts in world language teaching.
Split Shifts From Gantt View in the Odoo 17Celine George
Odoo allows users to split long shifts into multiple segments directly from the Gantt view.Each segment retains details of the original shift, such as employee assignment, start time, end time, and specific tasks or descriptions.
How to Handle the Separate Discount Account on Invoice in Odoo 17Celine George
In Odoo, separate discount account can be set up to accurately track and manage discounts applied on various transaction and ensure precise financial reporting and analysis
Ardra Nakshatra (आर्द्रा): Understanding its Effects and RemediesAstro Pathshala
Ardra Nakshatra, the sixth Nakshatra in Vedic astrology, spans from 6°40' to 20° in the Gemini zodiac sign. Governed by Rahu, the north lunar node, Ardra translates to "the moist one" or "the star of sorrow." Symbolized by a teardrop, it represents the transformational power of storms, bringing both destruction and renewal.
About Astro Pathshala
Astro Pathshala is a renowned astrology institute offering comprehensive astrology courses and personalized astrological consultations for over 20 years. Founded by Gurudev Sunil Vashist ji, Astro Pathshala has been a beacon of knowledge and guidance in the field of Vedic astrology. With a team of experienced astrologers, the institute provides in-depth courses that cover various aspects of astrology, including Nakshatras, planetary influences, and remedies. Whether you are a beginner seeking to learn astrology or someone looking for expert astrological advice, Astro Pathshala is dedicated to helping you navigate life's challenges and unlock your full potential through the ancient wisdom of Vedic astrology.
For more information about their courses and consultations, visit Astro Pathshala.
Is Email Marketing Really Effective In 2024?Rakesh Jalan
Slide 1
Is Email Marketing Really Effective in 2024?
Yes, Email Marketing is still a great method for direct marketing.
Slide 2
In this article we will cover:
- What is Email Marketing?
- Pros and cons of Email Marketing.
- Tools available for Email Marketing.
- Ways to make Email Marketing effective.
Slide 3
What Is Email Marketing?
Using email to contact customers is called Email Marketing. It's a quiet and effective communication method. Mastering it can significantly boost business. In digital marketing, two long-term assets are your website and your email list. Social media apps may change, but your website and email list remain constant.
Slide 4
Types of Email Marketing:
1. Welcome Emails
2. Information Emails
3. Transactional Emails
4. Newsletter Emails
5. Lead Nurturing Emails
6. Sponsorship Emails
7. Sales Letter Emails
8. Re-Engagement Emails
9. Brand Story Emails
10. Review Request Emails
Slide 5
Advantages Of Email Marketing
1. Cost-Effective: Cheaper than other methods.
2. Easy: Simple to learn and use.
3. Targeted Audience: Reach your exact audience.
4. Detailed Messages: Convey clear, detailed messages.
5. Non-Disturbing: Less intrusive than social media.
6. Non-Irritating: Customers are less likely to get annoyed.
7. Long Format: Use detailed text, photos, and videos.
8. Easy to Unsubscribe: Customers can easily opt out.
9. Easy Tracking: Track delivery, open rates, and clicks.
10. Professional: Seen as more professional; customers read carefully.
Slide 6
Disadvantages Of Email Marketing:
1. Irrelevant Emails: Costs can rise with irrelevant emails.
2. Poor Content: Boring emails can lead to disengagement.
3. Easy Unsubscribe: Customers can easily leave your list.
Slide 7
Email Marketing Tools
Choosing a good tool involves considering:
1. Deliverability: Email delivery rate.
2. Inbox Placement: Reaching inbox, not spam or promotions.
3. Ease of Use: Simplicity of use.
4. Cost: Affordability.
5. List Maintenance: Keeping the list clean.
6. Features: Regular features like Broadcast and Sequence.
7. Automation: Better with automation.
Slide 8
Top 5 Email Marketing Tools:
1. ConvertKit
2. Get Response
3. Mailchimp
4. Active Campaign
5. Aweber
Slide 9
Email Marketing Strategy
To get good results, consider:
1. Build your own list.
2. Never buy leads.
3. Respect your customers.
4. Always provide value.
5. Don’t email just to sell.
6. Write heartfelt emails.
7. Stick to a schedule.
8. Use photos and videos.
9. Segment your list.
10. Personalize emails.
11. Ensure mobile-friendliness.
12. Optimize timing.
13. Keep designs clean.
14. Remove cold leads.
Slide 10
Uses of Email Marketing:
1. Affiliate Marketing
2. Blogging
3. Customer Relationship Management (CRM)
4. Newsletter Circulation
5. Transaction Notifications
6. Information Dissemination
7. Gathering Feedback
8. Selling Courses
9. Selling Products/Services
Read Full Article:
https://digitalsamaaj.com/is-email-marketing-effective-in-2024/
Principles of Roods Approach!!!!!!!.pptxibtesaam huma
Principles of Rood’s Approach
Treatment technique used in physiotherapy for neurological patients which aids them to recover and improve quality of life
Facilitatory techniques
Inhibitory techniques
Credit limit improvement system in odoo 17Celine George
In Odoo 17, confirmed and uninvoiced sales orders are now factored into a partner's total receivables. As a result, the credit limit warning system now considers this updated calculation, leading to more accurate and effective credit management.
Understanding and Interpreting Teachers’ TPACK for Teaching Multimodalities i...Neny Isharyanti
Presented as a plenary session in iTELL 2024 in Salatiga on 4 July 2024.
The plenary focuses on understanding and intepreting relevant TPACK competence for teachers to be adept in teaching multimodality in the digital age. It juxtaposes the results of research on multimodality with its contextual implementation in the teaching of English subject in the Indonesian Emancipated Curriculum.
21. JIRA Demo
Try JIRA on your own!
JIRA OnDemand
www.atlassian.com/software/jira/try/
22. Questions?
Maija Ļaksa
maija.laksa@ebit.lv
www.ebit.lv
Editor's Notes
JIRA is one of the tools developed by Atlassian company (http://www.atlassian.com/). There are more than 18’000 companies world wide using Atlassian tools.And these tools are also quite familiar in Latvian IT community.There are several tools provided by Atlassian. The most popular are:JIRA – tool for project and issue trackingPluginsGreenhopper – tool for agile project managementBonfire – tool for Exploratory testingConfluence – a wiki tool for collaboration and content sharingSeveral code quality tools – Bamboo, Clover, Crucible, FishEyeBonfire is dedicated plugin for JIRA to be able to manage testing.Unfortunately this is commercial plugin and will require additional costs.What can we do about test management in JIRA and not willing to invest money in other tools?
Let’s start with introduction to some basic concepts in JIRA.Each document or issue in JIRA has an issue type.Most popular are the ones related to application maintenance – incidents, problems, service requests, change requestsThere can be unlimited types of issues defined in JIRA: - Change Request - Incident - Problem - Service Request - User Stories - ...
Another important concept in JIRA is workflow.There can be unlimited number of workflows defined.For each issue type in JIRA project there can be a particular workflow associated.New workflows can be easily defined. For each transition between statuses there can be 1) screens containing particular fields configured which can be filled in when transition is executed2) a performer set - user role provided which can perform a transition3) post fuctions defined which will be executed – for example – update value of the particul field, perform additional actionsWhen issue has been created, it has a status – in a sample case – Open.On the final status it is possible to set resolution for the issue, so that it disappears from the operational views in JIRA.
There are two types of relationships available in JIRA by defaultWhen new issue is created it is a Main issueFor Main issue there could be sub-tasks created - if there are several activities to be performed to solve the issueJIRA default configuration allows only 2 levels in issue hierarchy. Sometimes it seems to be a kind of limitation, however it is possible to adjust mindset to the limitation and find a solution to be enough with two levels issue hierarchy. Data fields can be used to categorize issues and group relevant ones together.Links – any two issues can be linked to show relationship between them
Last key concept in JIRA is Versions. Putting issue to the version, JIRA allows to monitor readiness or maturity of the version, called “Road Map”There can be different use of versions – in Maintenence projects these could be releases which are defined as versions – e.g - R12.2 - R12.3However, these could be also Project phases which are defined as versions – e.g. - System Test - User Acceptance TestThere could be also additional version created for Administrative tasks in the project.--------------------------------------Now you have beed introduced to basic concepts in JIRA – issue types - workflows - relationships between issues - versionsNow I’m going to discuss how the same concepts can be used also for testing management not only issue and project tracking.
As the first step to configure JIRA to support Test management is to define new issue types.On the main level we defined one issue type – TestOn Sub-task level we defined Test* and Acceptance Test*We put * at the end of issue type because issue type name should be unique in JIRA. But still we wanted to have issue type names similar to be easier used in searches afterwards.
To maintain Testing Phases we used two approaches:Define Versions to correspond to Testing Phases:System TestUser Acceptance TestORUse different issue types for Tests performed by Supplier team (Test*)Customer team (Acceptance Test*)
Let’s check key elements on JIRA issue:Issue Type – TestFix VersionsLinked issuesSub-tasks
To supporttest management we have defined a new workflow. We used the same workflow for all issue types related to testing.To define Issue statuses for test management we prefixed all test related statuses with ���Test:”This helped to sort test related statuses together in JIRA reports and views.The first 2 statuses can be used while in Test planning phase – to start to create tests and sub tasks as early as possible in the project, which will be part of test plan – to document all tests which will need to be executed.At planning phase all issues can be assigned to test manager, and then, when decided who will test what – tests can be re-assigned to the actual tester and issue can be moved in wirkflow to the step “Test: Ready to Run”Or test can be assigned to dedicated tester if there will be needed to provide detailed information about what test activities will be performed.The following statuses are related to Test Execution: - In Progress, ....There are 2 final statuses in Test workflow where resolution will be set: - Test: Passed – Resolution = ‘Fixed’ - Test: Obsolete – Resolution = ‘Won’t fix’
This is how test related statuses look like on JIRA online reporting gadgets.
Let’s check key elements on JIRA issue:Issue Type – TestMaster issue number / sub-task issue number Issue Status / Resolution / Fixed versionsWorkflow actionsDescription == test steps, test procedure – free formattingTest results as screenshots
Attached screenshots can be easily reviewed.
Let’s check key elements on JIRA issue:Issue statusWorkflow actionsLinks to related issues
Let’s check key elements on JIRA issue – discovered failure during test execution:Links to related issues
There is Clone and Move functionality in JIRA which allows to create copy from System Test to Acceptance test
Sample online reports available in JIRA – pie charts
Sample online reports available in JIRA – two dimensional filter statistics - Issue statistics
Samples demonstrated so far were suitable for development or implementation projects where testing is a separate project phase and testing tasks are planned independently from reported issues.In application maintenance projects testing is closely related to reported issues.In such cases testing activities can be created as sub tasks to the reported incident or problem, or link between problem and test can be created: Problem .. is tested by Test .. is testing
JIRA allows to monitor maturity of the version – Road mapIt shows number of Fixed issues linked to the version and issues still in progress
!!!!DEMO!!!!https://jira.ebit.lv/secure/Dashboard.jspazane.odzina@ebit - Dashboards -- Test -- All - Project roadmap - Project summary