Excellent Feature and nice to have in RTC
Imagine a scenario like each of our Test Engr/Analyst attach a file while logging a Defect/task. yes RTC already has this capability to attach a file/screenshot. but all of my attachment size goes in to the RTC Database repository and the DB increases day by day. performance may be issue after sometime.
When i explore i also found that i can just indicate the link of the file instead of attaching the file, and the file can be put in to some share location. but the difficulty in today's world everybody need the automation. No developer wants to go more than 1 step while attaching a file only. step-1, keep the file in share location Step-2: copy the URL link(UNC Path- step-3: paste in the RTC (click on links tab in a defect and add related artifacts) tooooooo much thats what the developers feel. Solution: may be what I can think about, why not RTC gives the facility to attach the file by keeping in some other share folder automatically and create the link(URL). This way my DB will not grow and all attached files will be in separate folder which i also needs to be take care while taking the regular backup of DB & RTC. I would like to know is there any other tools provide the similar functionality if not RTC. Lets also discuss about the advantage and disadvantage of having this features. |
2 answers
Imagine a scenario like each of our Test Engr/Analyst attach a file while logging a Defect/task. yes RTC already has this capability to attach a file/screenshot. but all of my attachment size goes in to the RTC Database repository and the DB increases day by day. performance may be issue after sometime. This is an interesting idea - but I would be concerned about having important data that may get overlooked and not backed up over time. By having everything in the repository - at least you know it is always going to be there. I am less concerned about the effect of having attachments on the database. Databases are supposed to handle large amounts of data :-) I am not sure if you are saving much by having them on another file share - that takes space too. If you really want to add a link (URI) - then you can add this to the description or comments where it is less harmful. But let's continue the discussion - and hopefully others will join in. anthony |
Also, if there is a provision just for a link to a file at a shared location rather than attaching it and uploading to a repository then what if a stakeholder (or any user), for example, doesn't have access to the shared path where the file is stored? I think RTC should have both the features - linking to a file in a shared folder and attaching (uploading) a file.
Thanks! |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.