Skip to main content

Templates for JIRA

Fill required details in place of <> in the template

Filing JIRA

Use the below template while filing JIRA:

Lab info

Lab:

<Server name> e.g., NA productions

Loads:

<Server load> eg., CPaaS 2.1.4

<Browser with version> e.g., Chrome Version 72.0.3626.121(64-bit)

Timestamp:

<Date and time in EST> e.g., March 17, 2019 8:10-8:25 PM EDT

Setup:

e.g.,

URL: https://project.company.com/

Account: test@ask-mail.com

Password: Test@123

Steps:

<Mention all the steps in number bullet points>

Actual Result:

<>

Expected result:

<>

Reproducible:

<Yes/No with comment> e.g., Yes, but with trial accounts only

End User Impact:

<Adequately assess the impact of this issue on end-user> e.g., It would heavily impact the performance of call under specified scenario

Frequency:

<occurance rate> say., 100%

Fault Isolation:

<If you know which module the fault is> otherwise say., None


Validating JIRAs

Steps to verify:

Login to server <Staging URL/Production URL> with account <email id/password>

<1. ...

... n.>

Narrate the clear steps to verify the JIRA

Expected results:

<> write clear notes on what should be the expected results aligning with Jira requirement. If you are not sure of the req, bring it to the discussion on JIRA itself.

Actual results:

<> say., works as expected, if not mention the actual result observed.

Date/Time of test:

<> Eg., March 26, 2019 10:30 AM EST.

Conclusion:

<PASS/ FAIL>

Next,

Move the JIRA to “ TESTING DONE ” status if the test is a pass, Assign Jira to Project Admin.

If the test fails, keep the JIRA in ‘TESTING’ state and assign to Project Admin clarifying the requirement, Jeff may want to correct steps or take further action in redoing development changes. Repeat testing if required.

Comments

Post a Comment

Popular posts from this blog

Unlock protected blocks in Siemens SIMATIC Step 7

Recently I'd been called by Hindalco's Fabrication Plant division to unlock the protected blocks in Siemens SIMATIC Step 7. They were in need to unlock those blocks since an year because of 1 million Rupees of loss per month. They want to re-program those blocks but it was locked by the man who'd done the setup. From the people working in that department, I came to know that they were trying to call that man (someone from Italy) right here but he's not coming. Actually, what he'd done was that he'd locked some of the blocks and deleted the source file. And Siemens didn't provide any feature to unlock. Department people also told me that even the people working in Siemens don't know how to do it. Being a software engineer I know that any thing can be reverse engineered. So I took up the challenge. How did I unlocked the blocks? The first thing I'd done was searched about this software at Google and read about what is this software all about. Aft
50 comments
Read more

JS: The complete code example of Crypto.js (DES)

For one of the project I was trying to use crypto.js but I found that the Quick-start Guide have some deficiency in terms of library usage. So I am writing it here as a useful note for memory recap. <script src="http://crypto-js.googlecode.com/svn/tags/3.1.2/build/rollups/tripledes.js"></script> <script> var encrypted = CryptoJS.DES.encrypt("The secret message", "secret_key"); var e_msg = encrypted.toString(); console.log(e_msg); var decrypted = CryptoJS.DES.decrypt(e_msg, "secret_key"); var d_msg = decrypted.toString(CryptoJS.enc.Utf8); console.log(d_msg); </script>
4 comments
Read more

How to convert JIRA story into sub-task or defect?

Many times we entangled in the situation where we have made a  story  in JIRA but later on realised that it should have to be  defect  or in other case,  sub-task  of another  story . Story → Sub-task So the workaround for converting the story into defect is given below: Open your  story Click on  more  option Click on the  Convert to sub-task  option in the dropdown You would be asked to choose  Parent  story, so chose relevant story After submit, your  story  gets converted into  sub-task Story → Defect Now if you want the story to be converted into defect, then you should first convert it into sub-task. Thereafter, you can convert that sub-task into defect as given below: Open the  sub-task Click on  more  option Click on the  Convert to issue  option in the dropdown You would be asked to fill up relevant fields required for raising a  defect , fill them up as required After submit, your  sub-task  gets converted into  defect .
Post a Comment
Read more