Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Won't individual reports get out of sync?

TheLQ
– TheLQ

2011-01-04 14:05:44 +00:00
Commented Jan 4, 2011 at 14:05
They can, and that's one of the downsides. It's up to developers to keep them in sync (assuming an OTRS ticket and a TFS task NEED to be word for word...two or three OTRS issues may map to one TFS bug, for example). The reason we use this approach is we have a separate IT team that monitors OTRS for other issues and can assign issues to the dev team. If you're a shop that JUST writes/sells software, then I'd go with how Codeplex works. They integrate codeplex.com with TFS directly, so any issues submitted to the site automatically show up in TFS.

Ryan Hayes
– Ryan Hayes

2011-01-04 14:13:18 +00:00
Commented Jan 4, 2011 at 14:13

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »