Re: [Suggestion] Deactivate Jira Rich Text Editor

[Sergio Fernández <se...@salzburgresearch.at>]

Not sure if you already asked to INFRA, but don't waste their time, the 
plugin is not supported for Jira 6.x (ASF is currently using 6.1):

https://bitbucket.org/bbaker/atlassian-markdown/issue/9/jira-6-support

Would be cool is someone could take-up the implementation of such 
feature ;-)


On 22/10/13 08:50, Andrea Di Menna wrote:
> What about this?
>
> https://blogs.atlassian.com/2012/03/markdown-support-for-jira/

> Il 22/ott/2013 08:01 "Sergio Fernández" <
> sergio.fernandez@salzburgresearch.at> ha scritto:
>
>> Hi,
>>
>>   On 21 October 2013 21:33, Fabian Christ <ch...@googlemail.com>**
>>>> wrote:
>>>>
>>>>> I have been looking in the JIRA administration but could not find any
>>>>> possibility to change this ourselves.
>>>>>
>>>>
>> No, you have to request it to INFRA. I know it because I had to do it in
>> the other way around (enable it) for Marmotta (see INFRA-6858).
>>
>> It's funny, we discussed that f2f when yesterday Rupert realized about
>> such feature. I know he has his strong arguments (copy&paste directly from
>> issues to the documentation); but personally I'd prefer to have rich format
>> in the issues, and then translate to proper documentation. After all,
>> issues receive comments, documentation should be something more elaborated.
>> But, as I said, that's my personal point of view.
>>
>>
>> On 22/10/13 06:32, Rupert Westenthaler wrote:> Hi Enrico,
>>> On Mon, Oct 21, 2013 at 11:56 PM, Enrico Daga <en...@gmail.com>
>>> wrote:
>>>> maybe I missed something, but I remember Jira had a nice way of
>>>> keeping track of related commits, with detailed logs from svn.
>>>> I can't see it in the new version. Is this a known issue?
>>>> If we are preparing a wish list, I'd love to have them back...
>>>
>>> I think the SVN plugin was deactivated by INFRA about a year ago
>>> because it regularly crashed the Server.
>>
>> Track the commit related to issues is quite useful, I agree. So, what
>> about a different solution? What about switching to git after the imminent
>> release? Even if not all people is familiar now with such SCM, I think the
>> project could benefit of adopting it.
>>
>> Cheers,
>>
>> --
>> Sergio Fernández
>> Senior Researcher
>> Knowledge and Media Technologies
>> Salzburg Research Forschungsgesellschaft mbH
>> Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
>> T: +43 662 2288 318 | M: +43 660 2747 925
>> sergio.fernandez@**salzburgresearch.at<se...@salzburgresearch.at>
>> http://www.salzburgresearch.at
>>
>

-- 
Sergio Fernández
Senior Researcher
Knowledge and Media Technologies
Salzburg Research Forschungsgesellschaft mbH
Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
T: +43 662 2288 318 | M: +43 660 2747 925
sergio.fernandez@salzburgresearch.at
http://www.salzburgresearch.at