It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,883
×10,914

question asked: Sep 21 '17, 6:04 a.m.
question was seen: 1,357 times
last updated: Sep 21 '17, 12:38 p.m.

Related questions

Enabling RTC Rich Work Item editor affects reading description via Java API

1
Marko Tomljenovic (316●50●109) | asked Sep 21 '17, 6:04 a.m.

Hello,

we would like to enable the better text editor support in our 6.0.4 installation.
We do have quite a big amount of scripts/Java tools that are creating/changing work items on the fly.

Now we are wondering what consequences the activation of the rich text editor support we have to face when e.g. using one of our tools to change the description of a work item.

Comments
Ulf Arne Bister commented Sep 21 '17, 7:23 a.m.

Good one.
I think the answer is pretty vital to us. Once we have the cycletime I will immediately look into this (or hope somebody answered this already)

- Arne

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Karthik Krishnan (889●9●123●165) | answered Sep 21 '17, 9:27 a.m.

Our observations in 6.0.3 when enabled the rich text editors:


-- Our automation which read description went for toss as it was returning HTML tags.
-- Our script needed to be changed to handle this.

In the end, we dropped the idea of using rich text editors due to extra effort to adapt our scripts.

Comments
Marko Tomljenovic commented Sep 21 '17, 12:38 p.m.

Do you mean in the Java API the call to IWorkItem.getHTMLDescription() and then the calls to XMLString.getPlainText() and getXMLText()?

Where did you get HTML tags, in the getPlainText()?

Your answer

Register or to post 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.