DEV Community: Grace Icay

Mentorship in Tech

Grace Icay — Tue, 27 Feb 2024 00:09:30 +0000

Why having a Mentor matters in Tech

Cover Photo by Amy Hirschi on Unsplash

What is a mentor?

n: A trusted counselor or guide

Tutor, coach

Source: Merriam-Webster Dictionary

Mentor vs. Teacher

What is the difference between a mentor versus a teacher then?

While both mentors and teachers can be experts in specific subject areas, mentors may have a broader range of experiences and expertise than teachers as they are not necessarily experts with academic backgrounds, but with niche knowledge and skills as well.

With Mentors, there’s an emphasis on “guidance” rather than direct teaching. While teachers have specific disciplines that they teach, mentors’ goals can be more flexible as they don’t focus on academia and can be more closely related to a mentee’s personal goals.

Why look for a mentor?

Why should you personally seek out a mentor? Here are some benefits that you should consider:

Seek Advice and Guidance for Career Development (e.g. How do I get into tech?; I’m overwhelmed with resources, where should I start?)
Knowledge Sharing
Industry Insights (e.g. When’s the best time to apply for a job?)
How to Write Better Resumes
How to craft better portfolios
Learn Best Practices
Practice for job interviews
Problem-solving (e.g. I'm having a hard time brainstorming for better solutions to this problem, can you please help me have a look at it?)

Why Be a Mentor?

Do mentors even get anything out of being a mentor? A lot of people have asked me if there are even any benefits to becoming a mentor and that it's not just a waste of time. Here are some lessons that I've gotten from personal experience as well as from other mentors:

Give back to the community - I don’t think anyone would be where they are now without help from someone or a community. Why not give back?
Develop New Skills - as you go higher up the ladder, more transferrable skills are needed. Some skills that you will be learning as a mentor:
Leadership
Coaching
Empathy
Build Confidence - being a mentor can help build confidence in yourself. This doesn’t mean you can completely get rid of imposter syndrome, that's a completely different story altogether.
Gain a fresh perspective - it might have been a while since you last applied for a job, so it would be good to also learn from your mentee what industry or hiring practices they have noticed recently. Mentorship is a two-way street, you’re both learning from each other
Keep updated with industry knowledge. As tech is ever-evolving, it's hard to keep up with what technologies other industries or companies use in their day-to-day operations. Sharing industry knowledge is not something mentors can do, but mentees can as well.

Mutual Benefits

Moreover, there's an additional benefit to both sides, including:

Fosters a culture of collaboration and continued learning
Gain connections - Networking is an important skill and establishing connections in the industry could go a long way.
*Accountability *- Having a mentor-mentee relationship creates a sense of accountability for both as well as for each of their personal goals.
*Endorsement/Referral *- As the mentor has had the chance to work with you the mentee, each of them can endorse each other on LinkedIn to bump up their reputations. Just a word of caution (as I've seen someone do this) : it might be crossing the line to be asking your mentor for a visa referral as they are not your employer.

Types of Mentorship:

Short-term - up until you reach a certain goal; usually lasts one session but can be up to a few months
Long-term - repeated sessions that can extend for a longer time, usually 6 months or more

Dos

Take the initiative to look for a mentor. The first step is always to recognize that you need help. The next step is to take the time to seek help.
Clarify your goals. What’s your ask? Why are you seeking mentorship? clarify this with your mentor so they can help craft a growth planner for you.
Commit to the Task. A mentorship is a commitment that you need to adhere to to achieve your short-term or long-term goals. Put in the effort to be able to achieve your results.
Respect each other's time. Both mentees and mentors need to consider time as a valuable resource. If you're not going to be able to make a session, give them a heads-up as soon as you can.
Follow-up after a session. You can learn more by following up after the session, e.g. some questions you forgot to ask or some clarifications that you might want to know. But be respectful of each other's time as your mentor/mentee has a life outside of your sessions.
Get to know each other. As a mentor, it's important to know your mentee to be able to give advice that will resonate better with them. As a mentee, it's important to know your mentor to be able to understand where they're coming from with the advice they're giving.
Maintain the relationship - Keep your mentor updated with career successes and failures and ask for sessions when you think you need them.
Constant Feedback. As with software, it's important to keep a constant feedback loop to better understand what went wrong and what went right with the sessions. Sometimes some advice doesn't work while some do. Mentors are not infallible, and mentees' problems don't have the same solutions.

Where to find Mentors?

Your workplace. If your team or organization is not implementing a mentorship program, it's still a good place to start by asking a senior co-worker if it's possible to have them mentor you.
For people who are working in Japan or are looking to work in Japan, Tokyo Dev's Discord Community has a growing list of mentors
Online Mentorship Platforms
ADPList is a free mentorship platform where you can schedule 1-on-1 short-term or long-term mentorship sessions with an expert in the field that you wish to learn from. I am a mentor for QA here as well!
Thriving Elements connects ambitious high school students with STEM professionals to develop long-term relationships through a set curriculum and empower women in STEM.
Menternshift (formerly: 40-commit challenge). This is a non-profit project that I'm a part of, whose aim is to have mentees work on a software project with the help of a mentor. Currently, the first phase for this is ongoing so we are not accepting any applications for new mentees yet.
DEV has a Mentor Matching Monthly that just started this year. Look at their January post if you're looking for any mentors or would like to volunteer as a mentor.
Social Networks. LinkedIn is probably the de facto social networking site for professionals at the moment. As such, it's easier to look someone up on LinkedIn, cold-email them about a possible mentorship, and cross your fingers.
Networking Events. Having one-on-one talks with speakers at tech or networking events would probably open your mind to what kind of goals you want to achieve with the mentor. Some good tech events that I've been to here in Japan:

Women Who Code has a community in Japan open to English-speaking developers. I've had the chance to connect and have online discussions with WWCode Seoul and WWCode Taipei professionals as well through collaborative efforts from the WWCode team. They have both online and offline events for all of their communities and have cross-community activities as well.
Women in Tech Japan is an international community in Japan that aims to close the gender gap in tech and promote diversity and inclusion in Japan.
Creative Tokyo is not only for non-tech creatives but also for people working in tech in and out of Japan. They have online and offline activities, as well as an active Slack channel.

Power-charging Lightning Talks with AI Tools

Grace Icay — Fri, 05 Jan 2024 03:30:00 +0000

How to make your presentations and lightning talks more interesting

Photo by Andrea De Santis on Unsplash

As someone who has been attending Lightning Talk events as a listener and as a speaker, creating a visually appealing presentation is just one of the components to keep listeners interested in making a talk.

Among the most popular and widely used tools are Microsoft PowerPoint, Keynote, and Google Slides. But its basic features are too plain and too boring, and adding visually entertaining components could take a certain learning curve to implement.

With the rise of AI tools in tech, there’s even more chance of increasing productivity when using an AI-powered tool to create presentations.

Instant, for example, can be installed as a browser extension to power Google Slides with AI. But there are tons of available resources nowadays that do not limit us to add-ons to existing software.

Here are a few tools that I would recommend to power-charge your lightning talks with the help of AI

Gamma - I’ve started using Gamma since its public beta started last year, and I’ve been using it ever since. I initially started using it because of its markdown support and beautiful pre-made themes, but now it also makes use of AI in the form of a Design Partner and image generator.
At the moment, Gamma is available as a web app and as a Windows app.
Gamma is available for free but can be upgraded to Pro to get rid of the Gamma logo on the presentations and get more credits to generate images using the image generator.
Note: the provided link is an affiliate link. Signing up using the link may give me some compensation.
Beautiful AI - This is probably the most popular tool I’ve come across when looking at AI-supported presentation tools. It has a Designer bot to help generate presentations, outlines, and images. Beautiful AI is a paid service that requires a monthly subscription starting at $12 a month.
Tome - Tome makes use of a collaborative AI partner that can generate presentations based on entered prompts. It can also rewrite the text, adjust the tone, reduce the text, or extend it. Tome does not show its pricing model on its main page so I could only assume it’s available for free but also upgradeable to premium.
Decktopus - Aside from being a presentation generator, Decktopus also offers solutions for link-in-bio, microsite, sales funnel, mail signature link, portfolio, form, proposal, and lead generation.
Decktopus has a slide notes maker available to serve as a guide during presentations, as well as form inputs, a voice recorder, a custom domain, and a webhook.
Decktopus is a paid service that starts at $ 14.99/month for Pro AI. Currently, they are offering a 50% discount on all plans for students.
Slides AI - Unlike the previously mentioned applications, Slides AI is an installable add-on in the Google workspace and can be used directly with Google Slides.
With the basic plan, 3 presentations can be generated for free but it can be upgraded to a Pro or Premium Plan. Some upcoming features in Slides AI include an add-on for PowerPoint, document upload, and video export.
Pitch - Pitch lets users directly take video recordings to create video presentations. Aside from that, it also provides presentation analytics, engagement analytics, presentation embeds, and PDF and PowerPoint exports. It’s made available for teams to seamlessly interact with pitches and easily collaborate.
Pitch can be downloaded as a desktop application for Mac, Windows, iOS, and Android.
Deckify - Deckify makes use of a short, intuitive questionnaire to guide the user through the process of generating and customizing their presentation. It doesn’t look like it has completely customizable themes available aside from the range of color themes provided. There’s not enough information provided on the website regarding any available app integrations.
Deckify starts with a Free plan that has 2 presentations available but can be upgraded to a monthly or yearly plan at $10/month and $99/year respectively.

Summary

AI	Integrations	Templates	Themes	Pricing
Gamma	yes	yes	yes	yes
Beautiful AI	yes	yes	yes	yes
Tome	yes	yes	yes	yes
Decktopus	yes	yes	yes	yes
Slides	yes	no	yes	no
Pitch	yes	yes	yes	yes
Deckify	yes	no	yes	yes

Discussion of the Week #10

Grace Icay — Mon, 20 Nov 2023 02:00:00 +0000

Is getting promoted to management the only way for senior developers to go up in the ranks in a tech company?

FAANG companies have more levels of promotion compared to smaller companies, which is how more senior developers are able to go up in ranks while still staying in the company as a developer.

However, in Startups and even other non-FAANG big companies, senior developers end up having to get managerial positions even if they prefer more technical roles.

What are your thoughts on this? Share your discussion points in the comments below!

Discussion of the Week #9

Grace Icay — Mon, 13 Nov 2023 03:30:00 +0000

I first became active in developer communities this year, when I joined Tokyo Dev, Women Who Code Tokyo, and Creative Tokyo. I was able to become a lightning talk speaker for all three communities and was met with warm support from its members despite feeling imposter syndrome.

I was able to discuss what it's like working in Japan as a foreigner with the developers in Tokyo Dev, working as a woman in tech with Women Who Code, and bring out my creative side with the people from Creative Tokyo.

How important do you think it is to have a community of like-minded individuals in your journey as a developer? Share your experiences in the comments below!

Discussion of the Week #8

Grace Icay — Mon, 06 Nov 2023 03:00:00 +0000

Selenium is one of the most popular test automation tools and has stood the test of time for years.

Do you think there's a tool that will surpass Selenium's popularity any time soon? Share your opinion in the comments!

Discussion of the Week #7

Grace Icay — Mon, 30 Oct 2023 03:00:00 +0000

How do you stay updated with the latest trends and tools in tech?

Personally, I usually check the following websites:

ProductHunt to check new cool apps
DevHunt to check out new dev tools
Use the Daily Dev browser extension as a news aggregator
Future Tools for new AI tools
Check the Technology section of the Artifact app

Discussion of the Week #6

Grace Icay — Mon, 23 Oct 2023 06:00:00 +0000

Mac vs. Windows vs. Linux: What is the best OS for Software Development?

Sample categories for this discussion:

Web application development
Desktop application development
Mobile application development
An overall winner

Share your thoughts and let's discuss!

AI Generated text-to-video with Fliki

Grace Icay — Wed, 18 Oct 2023 09:00:00 +0000

I came across Fliki while looking for tools that could help me boost my social media presence.

It's a freemium tool (i.e. it offers a free tier while having other features up on a subscription paywall) that promises to make video creation easier by generating text-to-video with the help of AI.

The app is simple enough and easy to understand: link to a blog, type in ideas, link a tweet, or start everything from scratch. There are several use cases for this app, but I found the content creation one closest to my goal.

As a new user of the app, I have yet to explore other use cases of the app, but so far, I think it's good enough to use for simple videos for posting.

In this post, I've added a sample video that I've created using the app.

How do you think this app compares to other apps in the market? Share your opinions in the comments.

Creating Issues in GitHub

Grace Icay — Tue, 17 Oct 2023 03:00:00 +0000

Issue Management in GitHub

GitHub supports issue management out of the box. Users can create issues in a variety of ways and can even link pull requests to issues and resolve an issue automatically once a pull request is merged.

For most teams who don't have the option to subscribe to popular Project Management apps like JIRA, Asana, ClickUp, or Monday, you can make use of GitHub's issue management system to track the bugs in your application.

Additionally, GitHub also has a "Projects" feature that could connect to different repositories and serve as a task-tracking tool. Since it can be linked automatically to issues, it's easier to track not only tasks but also issues straight from GitHub.

GitHub projects provide the ability to create views and watch tasks as a Table, Board, or Roadmap, so users are free to configure Kanban Boards, Table views, or other ways they wish to view their tasks for their projects.

Issue Templates

Here are the steps you can follow to create templates for GitHub issues:

Open your GitHub repository

Click on the "Settings" tab
Under "Features", enable "Issues"
Click on "Set up Templates". GitHub automatically generates a Bug report template for the repository.
Click "Preview and Edit" on the Bug Report or Feature Request Template
Click on the Edit icon right next to the Bug Report or Feature Request Template title

Another way is to do the following:

Open your GitHub repository
Click on the "Issues" tab
Click "New Issue"
Click "Edit Templates". Click on the bug_report.md or feature_request.md to select which template to work on
Click on the Edit icon to edit the template.

GitHub supports markdown editing, so feel free to edit the contents of the template. If you wish to follow a sample format for filing bug reports and feature requests, I've come up with the following template that you can also use for your project:

Bug Reports

**Template Name:** Bug Report
**About:** Create a report to help improve the application
**Template Content:**

**Description**

<!-- A clear and concise description of what the bug is. -->

**Expected Behavior**
<!-- A clear and concise description of what you expected to happen. -->

**Actual Behavior**
<!-- A clear and concise description of what actually happened -->

**Steps to Reproduce**
<!-- A step-by-step guide on how to reproduce the issue -->

**Attachments**

<!-- If applicable, add screenshots or video links to help explain your problem. -->

**Minimal example**
 <!-- Link to minimal example, if applicable. eg: StackBlitz link -->

**Additional Notes**

<!-- Add any other remarks or context about the problem here. -->

**Issue Default Title:** [BUG]
**Labels:** bug

Feature Requests

**Template Name:** Feature Request
**About:** Suggest an idea to further improve the application
**Template Content:**

**Description of the problem**

<!-- Is your feature request related to a problem that you've encountered? Describe a clear and concise description of what the problem is. e.g.: I'm always frustrated when [...] -->

**Expected Changes**

<!-- A clear and concise description of what changes you would want to happen -->

**Additional Notes**

<!-- Add any other context or screenshots about the feature request here. -->

**Issue Default Title:** [FEATURE]
**Labels:** enhancement

Discussion of the Week #5

Grace Icay — Mon, 16 Oct 2023 09:00:00 +0000

Halloween is almost here!
Any spooky experiences at work? They could be related to coding or not, feel free to share them here!

Opinions on the new Fedora Slimbook Ultrabook?

Grace Icay — Fri, 13 Oct 2023 03:00:00 +0000

Okay, that's quite a mouthful. But recently, Fedora Project has announced its collaboration with Slimbook to deliver a new Fedora Slimbook Ultrabook that comes exclusively with Fedora Software.

Aside from the supposed better user experience that goes with shipping laptops with Fedora OS, the specs are also not too bad:

16” 16:10 sRGB 99%
3K display 90Hz
Intel® Core™ i7-12700H 20 threads
NVIDIA GeForce RTX 3050 Ti
Up to 64GB RAM
Up to 4TB Nvme SSD
82WH battery
1.5 kg weight

There don't seem to be any price points or estimates provided yet though.

Personally, I love Open Source Software and even though there is quite a learning curve when it comes to switching from Windows or MacOS to Linux, I've loved how easy-to-use and flexible Fedora has been. The GNOME community is also active with bug fixes and feature releases.

But, there are also other devices that ship with Fedora out-of-the-box, like Lenovo , so I'm wondering what kind of change this product release will bring to the market.

Let me know your opinions!

Creating Test Cases In JIRA with Tricentis

Grace Icay — Tue, 10 Oct 2023 03:00:00 +0000

How to create test cases in JIRA with the Tricentis Test Case Management Plugin

A Brief Introduction to JIRA

JIRA is a product of Atlassian and is considered one of the most popular project management and issue-tracking tools for software development and testing. It provides teams with a centralized platform to plan, track, and manage their projects, tasks, and issues.

The following are some benefits of using JIRA in software development:

Issue Tracking: JIRA allows teams to create and track issues throughout the software development lifecycle. "Issues" aren't only about bugs, but can also include feature requests, tasks, and so on. Each issue can be assigned to a team member, given a certain priority level, labeled, categorized, and tracked from the time it was created until a resolution is reached.
Project Management: It supports project creation and management, including capabilities to define project components, set up versions and milestones, and assign tasks to team members. This helps in ensuring transparency, collaboration, and timely completion of project milestones.
Agile Methodology Support: JIRA's flexibility enables it to support agile methodologies such as Scrum and Kanban, which can help agile teams easily visualize their workflow, manage their backlog, and adapt to changing requirements. Features like user stories, sprints, backlogs, and agile boards, allow teams to plan, prioritize, and track their work using agile practices.
Customization and Workflow Automation: With JIRA, users can customize labels, fields, workflows, and issue types based on their needs. It also provides support for workflow automation through its built-in rule engine, enabling teams to automate repetitive tasks, notifications, and workflow transitions.
Enables Collaboration and Communication: JIRA promotes collaboration and communication among team members by providing features such as comments, mentions, attachments, notifications, and in-app integrations with other collaboration tools to enable team members to discuss issues, share information, and provide updates.
Integration and Extensibility: JIRA offers various integrations with other development and testing tools. Source code repositories, continuous integration and deployment tools, and test management systems, are only some of the integrations that allow seamless data flow and synchronization between different tools, providing a unified project view.
Reporting and Metrics: JIRA provides reporting and metrics capabilities to track project progress, team performance, and issue resolution time. It offers built-in reports like burndown, velocity, and control charts, which are useful for monitoring and analyzing project data. Teams can use these metrics to identify bottlenecks, make data-driven decisions, and continuously improve their development and testing processes.

Tricentis

Tricentis Test Management for JIRA is an add-on that integrates the Tricentis Test Management solution with JIRA. It extends the capabilities of JIRA by providing advanced test management functionalities that are not native to the application.

Here are some benefits of using Tricentis Test Management for JIRA:

Test Planning and Design: The Tricentis Test Management tool allows teams to create and manage test plans, test cases, and test suites directly within JIRA. Created test cases are counted as "Issues" in JIRA and provided the "Test Case" Issue type. They can also be organized into hierarchical folders, tagged with relevant labels, and associated with requirements, user stories, or other issues in JIRA.
Test Execution and Tracking: Team members can execute test cases and track the results of manual and automated tests within JIRA. Test runs can be scheduled within releases, assigned to team members, and tracked for progress. Testers can record their execution status, and attach screenshots, screen records, logs, or other artifacts found during testing.
Traceability and Coverage: The tool provides traceability between test cases and requirements or user stories. This helps generate a Forward Traceability and/or Backward Traceability matrix for the teams to ensure that the test coverage aligns with the project requirements.
Test Metrics and Reporting: Teams can generate reports on test execution progress, test coverage, defect trends, and other relevant metrics to help stakeholders gain insights into the testing process, identify bottlenecks, and make informed decisions.
Integration with Automation Tools: Tricentis Test Management for JIRA integrates with various automation tools, such as Tricentis Tosca and Selenium, among others to allow teams to execute automated tests and synchronize the test results within JIRA. These integrations help streamline the testing process and provide a consolidated view of manual and automated testing efforts.
Import Test Cases: The tool enables importing test cases from an Excel file, following the required format prescribed in the sample template they provide. It's also possible to import test cases by integrating other services, but this is the native implementation of test case importing embedded into the tool

JIRA Issue Creation

Process

The following provides a step-by-step process on how to create an issue in JIRA

From the JIRA page, open the Project Dashboard
Click "Apps" from the navigation header
(Assuming that your JIRA administrator has enabled templates) Select "Create from Template".
To create a Bug ticket, select the "Bug" issue type and the Bug template you need to use. For Feature/Improvement Requests, select the "Code Task" issue type and the Template that you need to use.
If you're just creating an issue without using a template, you can skip steps #1-4 and create a ticket by clicking the "Create" button on the top of the global navigation menu.
Click the "Confirm" button. This will show a modal to provide values for dynamic variables (if the issue is created from a ticket)
Click the "Confirm" button to move on to the issue creation page.
Fill in the values for the issue.
Once the values are filled in, click the "Create" button.
Click "Close" to close the issue or "Confirm" to create another issue.

Values

Summary - Provide a quick overview of the issue
Assignee - Unassigned by default, or select an assignee (this would mostly depend on your organization's internal process)
Priority

Highest - urgent issues like issues affecting all customers, issues that cause the environment to fail, and issues with hotfixes required
High - customer requests or issues encountered by a group of customers
Medium - medium-level issues. In some tickets, these are tagged as "Normal" level issues due to labeling problems with integrated applications like GitHub.
Low - cosmetic issues, issues that aren't necessary to be fixed in the current sprint
Lowest - negligible issues, but having the fix for this would be nice to have

Affects Versions - the version affected by the bug. If it's found in the dev environment, add the pending release as the affected version. If it was found in the production environment, add the version number of the latest app release as the affected version.
Fix versions - the version when the fix for the specific issue was released or is planned to be released
Browser - The name of the browser being used when the issue was reproduced
OS - The operating system being used when the issue was encountered and/or reproduced
Attachment - The section where users can provide screenshots or screen recordings of the issue encountered
Description - A more in-depth description of the issue. The following includes a list of information that would be helpful to add to the issue description:
*Expected Results *- the expected result of the action done or the expected output of the feature
*Actual Results *- the actual result of the action done, or the actual output of the feature
*Steps to Reproduce *- a step-by-step description of the actions done to reproduce the issue
*Frequency Rate *- (Failure Rate/Trials Done)x100 = Frequency Rate (%)
Workaround - Workaround executed to mitigate the issue, if any
*Possible Root Cause *- a possible cause of the issue happening
*Fixes Done *- fixes that were done or will be implemented to resolve this issue
*Additional Notes *- Additional notes that are important to the ticket but weren't covered by the existing labels or descriptions, if any
Components - Specific component/s where the issue was found
Labels - optional, as this is usually dependent on the rules of the organization

Test Cases

Test Case issues are created to serve as the test cases for a project and can be reused throughout the project's life cycle. When using the Tricentis Test Management Tool with JIRA, these test cases are classified as "Test Case" issue types. The following are the configurations related to Test Cases created with the Tricentis tool:

Folder - As a standard, this should be named after the function, component, or page where the test case belongs to
Key - The Issue number, concerning the project where the test case is created
Summary - As a standard, it's helpful to make use of the test case number to keep track of the test case for the page where it belongs. Using other test cases as a guideline, this would then follow the format: <3-4 letters>-####
Description - A basic description of the test case to be executed. This doesn't need to be as elaborate as the descriptions of the bug tickets or feature request tickets.
Environment - The environment where the test case will be executed. For a web app, the following format could be followed: OS, Browser, and URL
*Pre-condition *- Pre-conditions or assumptions that are needed for the test to work
*Test Steps *- Steps executed for the Test Cases
*Step Data *- Data inputs needed to execute the test cases and get the expected results
Expected Results - Expected results of the steps executed
*Linked Issues *- link the related Requirements Issues to enable RTM Generation
*Requirements Issues *- Issues created for coverage checking. This serves as the Requirements Checklist
*Epic Issues *- specifications for the Requirements issues. These are big code tasks that need more than 1 sprint to be completed
*Code Task *- Feature Requests for better Usability, Navigation, etc. to improve user experience
*Sub Tasks *- Child tasks of Epic issues or code tasks
Components - related components from the application
Label - optional, but it would be helpful to categorize all tests under one label, such as testing
Type of Test **- Tricentis has two types of tests: **Functional or Non-functional. So choose whatever fits the description of the test being run best

Conclusion

Tricentis Test Case Management Tool is a helpful add-on for teams who already make use of JIRA for bug tracking and/or project management. Instead of looking for an external solution that might bring in additional third-party costs, it's important to consider how to improve existing systems first.

I hope this guide can help not only other testers looking for a test case management tool to integrate with JIRA but also those who want to improve their issue creation or ticket filing system in JIRA.