You may come across a situation where the base URL of your Spira instance has changed and the embedded image URLs no longer match. This will cause a broken image to display inside the various rich text editors in Spira. This article explains how you can use SQL to do a bulk update of the offending URLs.
When you need to embed an image inside the description of a requirement, test case, task, etc. you need to follow the process outlined in this article. With the release of SpiraTeam 4.0 you can then have these images appear in the PDF, HTML and MS-Word 2003 format reports.
This article is now obsolete.It is not required anymore to first upload the images and then specify the URL to display it in the description of the artifact (and then report) - all description fields are now rich text and screenshot images can be copied directly from the clipboard - the file will be automatically added to the description of any artifact.
When you run Rapise automated tests using RapiseLauncher the system will automatically embed the images from Rapise into the various test cases and test run reports. By default the report format has relatively small images so that they can fit easily into the tables of expected result and actual results. However some users have asked for ways to make the images bigger.
This article describes how you create / modify the XSLT report templates in Spira to include embedded images without having to manually embed them in the artifacts. It uses the ability of the XSLT reports to have an <IMG> tag in the report template that references the attachment URL.