After migrating a Test Case work item type, the attachments are no longer linked to the individual test case steps.
Before
After
The attachments are being migrated however, i.e. they are part of the work item attachment list.
Any help appreciated.
Attachments to test steps are not currently supported.
You can submit a PR with that feature.
Related
we want to add one disclaimer notes as below on 50 reports of splunk.. can we do that in one shot?
Disclaimer:- In case you do not find any attachment OR Blank attachment this means no matching events or Blocked events were found during the report scheduled time.
If you have access to the CLI then you can edit the savedsearches.conf file(s) to add that text. It should be faster than using the GUI.
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.
With our TFS 2015 source control we require developers to check-in changes against work items.
However, we've had a couple of instances where a developer has checked in against one work item within our development branch, but then when merging to our QA branch they've checked in the merged changes to a different work item. An example of this is where a bug has been created underneath a PBI, the changes in dev have been checked in against a task under the bug, but then merged to QA against the PBI itself. This causes us issues with traceability.
I've seen that it's possible to add a check-in policy of "Work Item Query Policy". I'm just wondering if there is a way to write a query that will determine if the work item of a check-in after a merge matches the work item of the source changesets? I'm not necessarily after the exact query (though it would be lovely if someone could provide one :) ), really I'm just wondering whether it's possible or not to have a query to do this - i.e. is the information available to queries in TFS?
You can't do this with the existing policies, you'd need to build a custom policy.
So, technically this is possible. You can access the VersionControlServer object through the PendingChanges object:
this.PendingCheckin.PendingChanges.Workspace.VersionControlServer
You can use that to query the history of the branch in question and grab the work items associated to the check-ins in that branch.
You can check the associated workitems to the current workitem:
this.PendingCheckin.WorkItems
You could probably even provide the option to auto-correct by adding the correct work items to the checkin upon validation.
One of my policies provides an example on using the VersionControlServer from a policy.
Okay this might be a interesting question but if there is a custom form people use on Outlook to submit files to be posted online, is there anyway (when the send button is pressed) to sync that file to a Sharepoint database (archive) of these file types?
These files are generally reports and we are trying to keep an archive of them without making it a two step process - 1. submit web request 2. then upload to archive.
The short but unhelfpful answer is - yes, you can do that. There are several APIs available for integrating with SharePoint that provide the ability to upload files. You can build this functionality in an Outlook COM Add-in. However, a lot more specifics are required for a more detailed answer.
Was wondering if anyone could help me out. I have written a report in SSRS 2008. I would like to add a button or a link on the page that will email the currently run report.
I know I can do this in subscription and set a schedule for this however the data needs to be checked before an email can be sent out.
Thanks for taking a look
Rusty
Essentially what you want to do is put a mailto link on the page that generates an email when the user clicks on it. There is a component of the mailto link which will include an attachment. However, the attachment must be a locally housed file, it cannot be stored at a web address. See more here.
If the report you are running does not require many resources, you can set up a subscription which will, on a scheduled basis (say every 5 minutes), write the report to a file on a shared drive. Therefore, the report is constantly being written and updated at a local path. Then, you should be able to use the "&attachment=" portion of the mailto link to refer to this subscription-generated file sitting somewhere on a shared drive. This might not be a good option for you if you're counting on up-to-the-second data in this report you're generating. Then again, if you're having the report manually reviewed by human eyes, then that's probably not too much of an issue.
If you pursue this solution, it will be important to keep in mind that whatever shared drive you have your subscription write the file to will need to be accessible by anyone that will be clicking on that mailto link. It's not sufficient for you to have access to it. When that mailto link is clicked, it will use Windows authentication (or authentication from whatever system you're using) to connect to that shared drive and retrieve the file.
Best of luck!