Hi Nita.
I meant that I was sent a PM, but I did not have any options to reply to the PM or create a new PM. I just checked again, and now I have reply options, but they weren't there this morning. Strange.
Thanks,
Jason
Search found 4 matches
- Wed Mar 29, 2017 9:35 am
- Forum: Single-Sourcing
- Topic: Best practice/workflow for tying changes to product version
- Replies: 11
- Views: 7607
- Wed Mar 29, 2017 4:44 am
- Forum: Single-Sourcing
- Topic: Best practice/workflow for tying changes to product version
- Replies: 11
- Views: 7607
Re: Best practice/workflow for tying changes to product vers
Another user asked for an update on the integration, but the forum would not let me reply. We are in the middle of testing Flare, but we are blocked by the import from Doc-To-Help not working (Support case in progress). However, our TFS administrators have done their own research and are very confid...
- Fri Feb 17, 2017 12:19 pm
- Forum: Single-Sourcing
- Topic: Best practice/workflow for tying changes to product version
- Replies: 11
- Views: 7607
Re: Best practice/workflow for tying changes to product vers
Thanks Greg. This isn't about old version vs new version. Changes for individual features within the same version must be kept separate from each other in order to keep some but not others. So each feature would need a unique tag, even if the feature is just renaming a field. That's a couple of doze...
- Wed Feb 15, 2017 7:14 am
- Forum: Single-Sourcing
- Topic: Best practice/workflow for tying changes to product version
- Replies: 11
- Views: 7607
Re: Best practice/workflow for tying changes to product vers
Greetings! I'm working with Mary (mwright123) to try and find a new documentation tool that meets both our needs. We have a potential solution, and we hope you can provide some feedback. Individually tagging changes would be nearly impossible for us. The additional work involved with tagging all cha...