I have tried different things and I know there are two ways of moving test cases from one Jira Project to another.
1. Manually move each test case by using option "move".
2. Exporting all the test cases in CSV format and then Import it to new project.
The problem with:
1st approach is that it is time consuming as there are thousand of test cases.
2nd approach- I don't see an option of exporting test cases in csv format, I only see xml, excel and printable. And while importing test case through "Test Importer" it only accepts csv format.
Is there a better way to move/copy test cases from one JIRA project to another?
You can do bulk edit and move all issues together. Here are the general steps:
Search using a query that gives all the issues you want to move(in your case it would look something like project = MyProject AND type = Test)
Click on the tools on top right corner and select bulk edit
select all issues you want to edit and click next
Select Move Issues from listed options and click next
fill required information and Jira should start moving all selected issues
Since there is no undo option, I would recommend moving one or two issue first to see it is working as you expected before making any bulk changes.
Related
I am new in this field and I am looking to download a single report, but it has more than 200 values in a drop down. Can you guide me how to download all the report with 200 values in one go.
Let me give you an overview of what the data looks like:
There are 200 practices and each practices has 5 or 6 providers. I am new in healthcare industry. So, I need to manually click on each practice and each provider and click on the view report to see the report and then download the report. So, we have run the report and click to save in PDF for all 1000+ reports.
We use the standard version of SSRs and we don't have any Enterprise version of it.
Can you guide me what to do in this case? Thanks.
I would recommend using a data-driven subscription to generate these reports. When you set up the subscription, you can provide a query that lists all the practices. When the subscription runs, it will generate a separate copy of the report using each practice as a parameter value.
You can set the subscription to email the reports or save them in a folder. This way, it doesn't matter so much how long it takes to run and there is much less manual work for you once you set it up.
You need to amend the report definition so that the filters allow for 'Select Multiple' that way you can select all in the drop downs.
So for example:
The option "Allow Multiple Values" would allow you to Select all of that parameter.
You can also use URL Access and pass in the parameter you want.
Go to http://<server_name>/ReportServer/ and find the report you want.
Then tack on to the end the parameter name and value you want. ¶m=val¶m2=val2
Then add the &rs:Format= command and put your desired extension like CSV.
e.g. http://<server_name>/ReportServer/Pages/ReportViewer.aspx?<my_report_path>¶m=val¶m2=val2&rs:Format=CSV
https://learn.microsoft.com/en-us/sql/reporting-services/pass-a-report-parameter-within-a-url?view=sql-server-ver15
If you have a lot of parameters, then run this through for loop. Python may be easiest.
We have one project in JIRA and we have uploaded all the issues under it. The issues are stored in the category wise structure.
For Example: Module 1 >> Test Cases
We want to fetch(copy) the test cases of few categories into another project. Is there any mechanism available in JIRA to copy multiple test cases in one go?
Kindly suggest the best possible solution of the above requirement.
There are a few options which may work for you:
You could try use the Structure Plugin for Jira:
Cloning Multiple Issues
Try a Marketplace plugin Bulk Clone Basic for Jira
Bulk Clone Basic Plugin
Another Try/Buy option Clone Plus Plugin for Jira
bobswift.atlassian.net/wiki/display/JCPP
Alternatively you could export the issues you need, adjust and then import as a new project:
confluence.atlassian.com/cloud/import-and-export-data-873871368.html
This functionality is still not supported in JIRA. The workaround mentioned in Tom's answer uses the Export/Import functionality, but, apparently, this does not copy any attachments (at least, not with JiraServer), so it is an unsatisfactory solution.
Unfortunately, AddOns appear to be the only option. Here's a list that shows the currently supported cloning tools in the Atlassian Marketplace. (At this writing, it looks like there are 3 or 4 options that promise to do the trick -- all "Try/Buy". I have not tested them.)
For those who aren't concerned about attachments, here's the detailed steps for exporting and importing to copy issues from one Jira project to another (in 2022 anyway).
In the source project, navigate to the Issues tab
Click the Export Issues button
Click Export Excel CSV (all fields)
Save the file in the dialog that appears
(Optional) Edit the CSV if you like although you can change some things in the import process
Click the ... in the top right
Select Import issues from CSV
Click Choose File
Select the CSV exported earlier
Click Next
Set "Import to Project" to your destination project
Click Next
Set fields you wish to map (e.g. Assignee, Components, Description)
Click Next
Click Begin Import
I found the solution for this
Search all the issue based on the filter.
Select all issue and top 3 dot select clone issue.
Follow the instruction and it moves all the issues.
I am trying to test the Login feature of my Android app with multiple user-password entries that I have in an Excel. I have already been able to import that data from the Excel successfully and run the same test with each row (with "Run on all Rows" option), but now I am facing a problem that I am not being able to solve.
After a test runs with one row, one the test starts over with a new row, it will not restart the app, but start at the same point where the previous one finished. I think this is not the expected behaviour, in general, since most of the GUI testing tools restart the app when testing a feature with parametrization (data from Excel, mostly). Anyway, I "fixed" this by logging out in my app.
In this case there was an "easy solution" by logging out. But what if I was testing a different feature in which I cannot simply "log out". The problem is that in those different cases I would have to navigate back or do something that may fail and has nothing to do with the feature I am testing.
I am not sure if I am not using the right approach. Is there a good general solution for this issue?
I would suggest the following two ways to solve your problem if you cannot simply use logout as the last step.
Use App.Launch function you can add one line to the top of your script like Device("iPhone 7").App("myApp").Launch NotInstall, Restart . Here the device and the app can be TO in object repository or identified using descriptive programing like Device("id:=123456")
Check options in Test Settings Please check the latest UFT version maybe 12.53 or later if there are any options in Test Settings for users to choose to restart or reinstall app for iterations.
Thanks
I'm trying to load data from my database into an excel file of a standard template. The package is ready and it's running, throwing a couple of validation warnings stating that truncation may occur because my template has fields of a slightly smaller size than the DB columns i've matched them to.
However, no data is getting populated to my excel sheet.
No errors are reported, and when I click preview for my OLE DB source, it's showing me rows of results. None of these are getting populated into my excel sheet though.
You should first make sure that you have data coming through the pipeline. In the arrow connecting your Source task to Destination task (I'm assuming you don't have any steps between), double click and you'll open the Data Flow Path Editor. Click on Data Viewer, then Add and click OK. That will allow you to see what is moving through the pipeline.
Something to consider with Excel is that is prefers Unicode data types to Non-Unicode. Chances are you have a database collation that is Non-Unicode, so you might have to convert the values in a Data Conversion task.
ALSO, you may need to force the package to execute in 32bit runtime. The VS application develops in a 32bit environment, so the drivers you have visibility to are 32bit. If there is no 64bit equivalent, it will break when you try and run the package. Right click on your project and click Properties and under the Debug menu you'll need to change the setting Run64BitRuntime to FALSE.
you dont provide much informatiom. Add a Data View between your source and your excel destination to see if data is passing through. Do do it, just double click the data flow path, select data view and then add a grid.
Run your app. If you see data, provide more details so we can help you
Couple of questions that may lead to an answer:
Have you checked that data is actually passed through the SSIS package at run time?
Have you double checked your mapping?
Try converting within the package so you don't have the truncation issue
If you add some more details about what you're running, I may be able do give a better answer.
EDIT: Considering what you wrote in your comment, I'd defiantly try the third option. Let us know if this doesn't solve the problem.
Just as an assist for anyone else running into this - I had a similar issue and beat my head against the wall for a long time before I found out what was going on. My export WAS writing data to the file, but because I was using a template file as the destination, and that template file had previous data that had been deleted, the process was appending the data BELOW the previously used rows. So, I was writing out three lines of data, for example, but the data did not start until row 344!!!
The solution was to select the entire spreadsheet in my template file, and delete every bit of it so that I had a completely clean sheet to begin with. I then added my header lines to the clean sheet and saved it. Then I ran the data flow task and...ta-daa!!! Perfect export!
Hopefully this will help some poor soul who runs into this same issue in the future!
Text was truncated or one or more characters had no match in the target code page.
how to avoid this error practically while import data from excel
In general, this could be caused by the fact that you have data that is too long in your source file compared to the field it is going into, the data is in different formats (source to destination), or something else in general like this. However, since you mentioned that it is coming from Excel, you might want to try this solution too, which works only for Excel:
Set your package to run in 32-bit mode. Click on Project on the top menu and select Data Imports Properties. Click on Configuration Properties -> Debugging and set the Run64BitRuntime to false.
This solution sometimes works for Excel projects, but it is an outside shot. If it doesn't work, try look at the data formats and fields in the source (and what they are being imported as).