Open siaalpha opened 3 years ago
shashankawasthi88
commented
3 years ago @siaalpha can you expand your workflows a bit more? Do these runs happen in Postman? What information do you foresee being put into JIRA? How will that streamline your flows? This would help us plan the Integration better.
ammar-ahmed-butt
commented
1 year ago Hey @shashankawasthi88 I hope you're doing well.
I think Integration with would Jira software would be really awesome, I tried it via webhooks and AWS CodeBuild Projects.
It's a bit lengthy workflow (😬 bear with me)
-- Work Flow 1
Branch is created on GitHub containing the Jira ticket id i.e. “JIRA-00:” ; automatically the ticket moves to "in progress" on the Jira Software board (In Progress is the ticket status). Comment is added on that jira ticket with time log as well, relevant users get tagged as well.
The “start date” field is filled with the current date. (Jira issue/Story/Task/bug ticket)
PR(Pull Request) is raised on GitHub, containing the Jira ticket id i.e. “JIRA-00:”; Automatically the ticket moves to PR Review on the Jira board, Comment is added on that jira ticket with time log as well.
Since the team lead is supposed to review the code, it automatically gets assigned to the lead, on the Jira board.
PR(Pull Request) is Merged on GitHub Comment is added on that jira ticket with time log as well.
Webhook Triggers (only on Three branches, develop, stage, master) AWS Codepipeline and the following process starts. E.g. Let's say if the branch is Develop to which PR is being Merged, and the ticket status changes to Deployed to develop on Jira
*AWS pipeline flow
Source (GitHub - PR Merge)(Branch - Develop)
Build
Deploy
Test
-- Postman - Newman (API testing) -- Cypress
If the pipeline ran successfully on AWS, a comment is added on that ticket which is on Jira Board, and that ticket is moved to Post Develop Testing ticket is assigned to the SQA, and manual testing is done.
Now the flaw in this workflow is that, it doesn't show or comment the test results which ran in the pipeline on the Jira ticket, for that I did find a solution, via APIs, the test results are added on jira ticket in .xml format, but haven't been 100% successful yet. 💀
Workflow 2
Everything remains the same till PR merge and webhook trigger AWS codePipeline ^
*AWS pipeline flow
Source (GitHub - PR Merge)(Branch - Develop)
Build
Deploy
If the deployment was successful on AWS, a comment is added on that ticket which is on Jira Board, and that ticket is moved to Deployed to Develop
From Jira a webhook is triggered, which will then create a monitor on the postman, run the test cases from the collection, and then sends the summary of test cases in response to that webhook.
Summary should get posted on that same Jira ticket, if 80% successful rate(which will be mentioned on the ticket) then the ticket transitions to "Post Develop QA", it gets assigned to the SQA, for further testing. (Trying to do this for the backend Deployment but haven't been 100% successful yet, for mobile apps using code magic, it was successful)💀
You can check this article, which I published back when I working on it. End to End Development process
-- In short a small Atlassian app, which does all this work, automatically.
Adds a comment on the Jira ticket, fetches via jira ticket ID just like GitHub, which was mentioned in the GitHub PR.
Comment should have a detailed report,(I also tried one more thing 😅, I'll tell that too).
Now here what happens, if any new API is created that is added in the collection on Postman with test cases. Through GitHub and Postman Backup integration it gets committed to the GitHub repo.
Then in both of these workflows, that new API also gets tested 🥹 Now I only need that test results/summary on Jira Ticket as well.
I hope this will help you to understand the need and importance of this app/integration. 😬😬😬
Describe your current workflow
Describe your ideal workflow
Jira intergation - would like to be able to dump all postman runs to jira for reporting options
Describe alternatives you've considered
none
Additional context
No response