Hoping to "mass load" issues from an older tracking system. Is 'BugNet_Issues' the only table I need to be concerned with? I already have users/status/priority/etc setup that I can hardcode in, so is it just a matter of slamming rows into BugNet_Issues with the proper ids for the foreign keys??Hi,
Thanks!
Not even that, just some assembly loading and minor stuff.Is the httpmodule uncommented in the web.config (2 places)?
When two users are logged in simultaneously, the tool doesn't have the ability to detect if another user is editing the same issue. As a result, the 'other' user can delete the issue which is being updated by another.BugNET uses optimistic concurrency by design which does not lock rows.
When user would edit the description, BugNET does not display all the value of the description. More or less, it only displays 40-50 characters.This is by design. An issue description could be a page of text which wouldn't look good in the issue history. An improvement would to highlight what has change doing a diff of some sort. Maybe one day.
In addition, BugNET should have the option on how many no. of rows the History tab will display.
Thank you.