If you haven't already, I recommend you check out my previous videos on how to create a Jira project. This video is the next logical step in my introduction to Jira series.

After you have created your very first Jira project, it is time to start exploring the user interface. Learning the basics here can really help you down the road. Knowing how to find the information that is most critical to you and being savvy on where things are contained within the world of Jira are going to give you an edge over your teammates.

If you like this video, please make sure to give it a thumbs up. If you haven't already, please consider subscribing.

If you have any questions about anything discussed so far, please feel free to make sure you leave your question in the comments section.

• Link to my other Atlassian Jira videos https://www.youtube.com/playlist?list=PLqWD37Mj2te2xeDcFWb4Vw1pvX5gHfWgy
• Link to my Atlassian Live Streams: https://www.youtube.com/playlist?list=PLqWD37Mj2te1QN1j7v-9jjCrp8Hty6dja
• Link to Atlassian's Jira products: https://www.atlassian.com/software
• Link to my Fiverr profile: https://www.fiverr.com/alexortiz924?up_rollout=true
• Link to my Upwork profile: https://www.upwork.com/freelancers/~01d55ed1a24784cd93
• Link to my personal website https://www.apetech.me/

Observability is a critical component of any Cloud development platform, and we have some exciting logging, monitoring, and debugging features planned for the Forge toolchain.

In this lightning talk, Senior Developer James Hazelwood from Forge infrastructure team will give an overview of Forge logging and tunnelling features, explain how different environment types effect observability, and share some expert tips and tricks for detecting and troubleshooting issues in your Forge apps.

• Once the storyboarding is completed,
• backlog is set up in Jira,
• tasks are assigned to development after you work out the estimates.
• Then it is time to ship the application to an initial release.

Agile teams across the world are familiar with Jira – the collaboration tool designed for issue and project tracking developed by Atlassian. While the basic use of Jira is to track issues, bugs etc. with your mobile and software apps, many teams have extended its use beyond just planning, managing and reporting.

For example, some DevOps teams like using Jira for test case management. And with a little creativity, a little customization, it can absolutely be configured to support manual test case management.

However, when it comes to supporting Test Automation in Jira, there is no direct way of doing that in Jira. The only way to incorporate or support Test Automation in Jira is by installing supporting apps from Marketplace in your Jira instance.

Now there are two categories of apps that could help your agile teams achieve test automation in Jira.

One is – Test Automation Apps. The problem with these apps is they only support automated test cases. Now to manage manual test cases, you will still have to rely on some other marketplace apps or do it in Jira as suggested earlier.

The other option is to install – an app from the category Test Management Apps.

QMetry Test Management for Jira (QTM4J) offers complete test management capabilities to Agile and DevOps Teams inside Jira. QTM4J provides powerful test authoring capabilities for Manual Testing as well as provides seamless integration with Automation tools.

QTM4J has integration capabilities with automation tools such as QAF/QAS that is QMetry’s Selenium based framework and IDE developed as part of contribution towards Open Source Community. It also allows integration with other automation tools such as HP UFT, Cucumber, Specflow, JUnit and TestNG.

So how does this Test Automation work inside Jira?

QMetry Test Management for Jira integrates with Automation Tools which then allows users to import automation test results into Jira.

Now there are two different ways of integrating with the automation tools –

• Users can directly import their automation test result (JSON/XML/Zip) files using a REST API as soon as the automation test gets executed, which creates a new test run in Jira with all associated test cases and results as executed in the automation test.
• QMetry can easily integrate with other CI/CD tools. There are ready made plugin available for Maven, Jenkins and Bamboo for importing test results.

So next question that arises is – How does Test case reusability work to avoid repeatability between manual and automated tests? This is how QTM4J ensures reusability –

• If Test case summary and Test step summary (for all steps) matches with the automated Test case, Test case key and version will be reused.
• If Test case summary matches and Test step summary do not match (for any of the steps) with the automated Test case, Test case key will be reused but new version will be created.
• If Test case summary does not match, new Test case will be created.

Combining the power of Jira and automated testing can remarkably speed up your cycles, improve collaboration and execute metrics that help with project delivery and visibility.

To see this in action, sign up for a free trial of QTM4J.

Don't forget to comment or reach out to me on Twitter if you have topics you would like to see me cover in the future: https://twitter.com/JimmyTalksJira Background music courtesy of

NDA: https://nda.band/songs/db/index.php ©NDA

Be sure to join the Atlassian Online Community, there are tons of Atlassian Customer just like you and me there to help each other every single day: https://community.atlassian.com/