I want to know if it possible to push subtask from DefectDojo to an existing issue or task int to existing JIRA project.
king regards,
Related
When some of my GithubActions jobs has failed, I don't have the possibility to re-run the specific failing job, only "Re-run all jobs". Is there any way to achieve this?
This is all working now in GitHub, the caveat is you can only run "specific jobs in a workflow run up to 30 days after its initial run."
https://docs.github.com/en/actions/managing-workflow-runs/re-running-workflows-and-jobs#reviewing-previous-workflow-runs
I’m the workflow file you want to be able to manually trigger, add workflow_dispatch to the “on:” clause. Then go to the actions tab on github, select the action and you should see the option to manually run it. Before asking this type of question, please use google next time. When looking for “triggger github workflow manually” the first result is a article written by github on how to do it. https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow
Unfortunately, re-run a single job is not possible yet.
Their repository does have an Open Issue to implement this feature.
https://github.com/actions/runner/issues/432
The good news is it is officially in their roadmap and is scheduled for Q1 2022.
https://github.com/github/roadmap/issues/271
I would like to exploit the integration between the two tools to be able to automatically create a branch in GitLab for every new Bug or Feature ticket created in Jira.
I would like to know if (i) it is possible; (ii) what is the link between the two tools (I guess the unique ID number assigned by Jira); (iii) assuming the first point is true, what happens to the created branch when I close the Jira issue (e.g. I've mistakenly created a bug fix that was not needed).
I've used Jira in conjunction with GitHub so I'll try my best to help you.
I) This is definitely possible.
II) We used to use the unique ID given to a ticket and include it within in the branch name this creates a link between both tools. Any changes committed on the branch will be shown in JIRA.
III) From experience when this happens the branch will persist and will need to be deleted manually using a console we used to use a .git console and used a delete command.
I also found through a quick google search some documentation on GitLab on integration with JIRA as well as some insight on creating branches.
Doc - https://docs.gitlab.com/ee/user/project/integrations/jira.html
Branch - https://gitlab.com/gitlab-org/gitlab-ce/issues/3886
Hope this helps.
I followed the next guide:
https://ecosystem.atlassian.net/wiki/display/FISH/JIRA+FishEye+Plugin+2.5.3+-+Perforce+Job+Integration
and successfully created a link between Perforce and JIRA.
I did manage to create a Perforce job on JIRA issue creation while selecting that option with the p4 job custom field.
What I cannot configure is a creation of a job automatically for each issue for a specific project as described in the next section:
Creating Jobs for ALL issues in a project
Another method of creating jobs (without the need to configure custom fields) is to set the Always create jobs for issues in this project flag in the project-level Perforce administration screen."
I can't find that flag for some reason.
Can anyone assist with screenshots or any other helpful information?
Eventually what I need to do is that for each issue that is created in JIRA a job should be created in Perforce.
Thanks in advance,
Max.
We want to create a defect/task in Jira automatically for a failed build in Bamboo. And need to assign this defect to the person who broke the build.
How to do these two things?
Thanks.
There is an open JIRA issue regarding this -- BAM-2537 -- watch it, vote for it - maybe they'll add it to the product.
The comments from Top 5 Reasons Creating JIRA Issues from Bamboo Makes Your Team Awesome-r also discuss what you're after.
Have a look at Atlassian CLI. There's already a good answer on StackOverflow.
Can Bamboo change status of tickets in JIRA
This is not "out of the box" solution, of course, and requires some additional work.
We have a JIRA instance installed on our side and our client is using that. Now client have purchased license of JIRA on Demand and want us to migrate their project from our JIRA to their.
Is there a way to achieve that?
Thanks in advance
Kaushik
Check out Altasian Splitting+a JIRA instance page:
Occasionally an organisation may need to split its existing JIRA instance into two separate instances. For example, there might be a requirement to have some particular projects in one JIRA instance, and other projects in a second instance.
Basicly, It's done by backing up the project and restoring it on the new server.
You will find a nice tutorial here:
http://www.jusuchyne.com/codingforme/2012/12/jira-migrating-certain-projects-from-instance/
As described here, there is a Plugin in the Atlassian Marketplace, that lets you copy the configuration: https://marketplace.atlassian.com/plugins/com.awnaba.projectconfigurator.projectconfigurator