OASIS Open Document Format for Office Applications (OpenDocument) TC

Hello Chet, we were running into some JIRA related questions on our last TC call, where you might assist us: We would love to have a notification on the OASIS ODF TC list whenever one of us has been editing an ODF TC related JIRA issue. Reason: We are sometimes surprised that someone worked on a JIRA issue and always explicitly writing to the list that we worked on JIRA seems awkward, right? We would love to have some enhanced JIRA editing functionality, e.g. some of us using JIRA in their projects with the WikiRenderer .  For instance, our new proposal on the this JIRA issue is quite hard to read in plain old text . We have been puzzled today if there is already a best practice of someone, how to map in JIRA TC states on mapping JIRA issue into their specification. Is there any good practice from other groups in a centralised place? I only stumbled over a very basic presentation file (1,34MB) . Thanks in advance for your help, Chet! Svante ?

Svante -  On Mon, Jul 3, 2017 at 10:40 AM, Svante Schubert < svante.schubert@gmail.com > wrote: we were running into some JIRA related questions on our last TC call, where you might assist us: We would love to have a notification on the OASIS ODF TC list whenever one of us has been editing an ODF TC related JIRA issue. Reason: We are sometimes surprised that someone worked on a JIRA issue and always explicitly writing to the list that we worked on JIRA seems awkward, right? You should be getting email notifications now. Do you not? If that is the case, I will have to debug the set up to fix whatever is wrong.    We would love to have some enhanced JIRA editing functionality, e.g. some of us using JIRA in their projects with the WikiRenderer .  For instance, our new proposal on the this JIRA issue is quite hard to read in plain old text . I will have to find out how much we can do here. I believe I looked into this last year and found that enhancing the interface would require licensing some add-on modules. But I will check again to be sure.    We have been puzzled today if there is already a best practice of someone, how to map in JIRA TC states on mapping JIRA issue into their specification. Is there any good practice from other groups in a centralised place? I only stumbled over a very basic presentation file (1,34MB) . I have attached the files that I have and hope they are helpful. We do need better documentation on the topic but these do go over basics.  Thanks in advance for your help, Chet! Sure. Again, if you are not getting notifications from JIRA please let me know.  /chet   Svante ? -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393  Attachment: JIRA-for-standards-dev-03-10-14.odp Description: application/vnd.oasis.opendocument.presentation Attachment: JIRA-for-standards-dev-03-10-14.pdf Description: Adobe PDF document Attachment: Best Practices for Issue Handling v9.docx Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document Attachment: Wier How to Jira.pdf Description: Adobe PDF document

On 03.07.2017 19:41, Chet Ensign wrote: > Svante - > > On Mon, Jul 3, 2017 at 10:40 AM, Svante Schubert > <svante.schubert@gmail.com < mailto:svante.schubert@gmail.com >> wrote: > > we were running into some JIRA related questions on our last TC > call, where you might assist us: > > 1. We would love to have a notification on the OASIS ODF TC list > whenever one of us has been editing an ODF TC related JIRA issue. > Reason: We are sometimes surprised that someone worked on a JIRA > issue and always explicitly writing to the list that we worked > on JIRA seems awkward, right? > > *You should be getting email notifications now. Do you not? If that is > the case, I will have to debug the set up to fix whatever is wrong. * hmm, i've added a comment just for testing about an hour ago, and i don't see a notification on the list. > 1. We would love to have some enhanced JIRA editing functionality, > e.g. some of us using JIRA in their projects with the > WikiRenderer > < https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all >. > For instance, our new proposal on the this JIRA issue is quite > hard to read in plain old text > < https://issues.oasis-open.org/browse/OFFICE-2119 >. > > *I will have to find out how much we can do here. I believe I looked > into this last year and found that enhancing the interface would require > licensing some add-on modules. But I will check again to be sure. * hi Chet, actually, since i brought up this topic, what i really want is a "plain text" renderer that actually does plain text properly :) as far as i can tell there is no way to paste something like an XML schema diff into a JIRA field without it getting its whitespace mangled such that it is very difficult to read. you have to actually log in an click "edit" on a field to view it properly. the WikiRenderer is documented to have "{noformat}" and "{code}" directives that should allow whitespace preserving display. alternatively, if JIRA allowed file attachments (without mangling them), that could well be good enough; i'm hoping that that's just an extra click, can open a new browser tab with a "text/plain" media type that the browser can display, and doesn't require login. at least, that's how attachments in Bugzilla work :) regards, michael -- Michael Stahl Software Engineer Platform Engineering - Desktop Team Red Hat Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com Red Hat GmbH, http://www.de.redhat.com/ , Sitz: Grasbrunn, Handelsregister: Amtsgericht München, HRB 153243, Geschäftsführer: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander

On 03.07.2017 22:12, Michael Stahl wrote: > On 03.07.2017 19:41, Chet Ensign wrote: >> Svante - >> >> On Mon, Jul 3, 2017 at 10:40 AM, Svante Schubert >> <svante.schubert@gmail.com < mailto:svante.schubert@gmail.com >> wrote: >> >> we were running into some JIRA related questions on our last TC >> call, where you might assist us: >> >> 1. We would love to have a notification on the OASIS ODF TC list >> whenever one of us has been editing an ODF TC related JIRA issue. >> Reason: We are sometimes surprised that someone worked on a JIRA >> issue and always explicitly writing to the list that we worked >> on JIRA seems awkward, right? >> >> *You should be getting email notifications now. Do you not? If that is >> the case, I will have to debug the set up to fix whatever is wrong. * > > hmm, i've added a comment just for testing about an hour ago, and i > don't see a notification on the list. this page looks quite useful as it lists all the most recent changes to our JIRA issues: https://issues.oasis-open.org/browse/OFFICE/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel it even has a "RSS" feed apparently, for those old enough to remember what that is :) -- Michael Stahl Software Engineer Platform Engineering - Desktop Team Red Hat Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com Red Hat GmbH, http://www.de.redhat.com/ , Sitz: Grasbrunn, Handelsregister: Amtsgericht München, HRB 153243, Geschäftsführer: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander

Hello Chet, thanks for your quick reply. Answers below. 2017-07-03 19:41 GMT+02:00 Chet Ensign < chet.ensign@oasis-open.org > : Svante -  On Mon, Jul 3, 2017 at 10:40 AM, Svante Schubert < svante.schubert@gmail.com > wrote: we were running into some JIRA related questions on our last TC call, where you might assist us: We would love to have a notification on the OASIS ODF TC list whenever one of us has been editing an ODF TC related JIRA issue. Reason: We are sometimes surprised that someone worked on a JIRA issue and always explicitly writing to the list that we worked on JIRA seems awkward, right? You should be getting email notifications now. Do you not? If that is the case, I will have to debug the set up to fix whatever is wrong.    As Michael already mentioned there is no update on the list. I worked on an issue yesterday and there is echo on the list: https://lists.oasis-open.org/archives/office/201707/maillist.html We would love to have some enhanced JIRA editing functionality, e.g. some of us using JIRA in their projects with the WikiRenderer .  For instance, our new proposal on the this JIRA issue is quite hard to read in plain old text . I will have to find out how much we can do here. I believe I looked into this last year and found that enhancing the interface would require licensing some add-on modules. But I will check again to be sure.    For Michael a whitespace-stable text would be sufficient, I thought a Monospace (or Fixed Font) will do it and offer text highlighting as well. I am currently sending mails to the list and reference from the JIRA issue to them. By this, I got HTML can attach documents (strange that this has been disabled as well in JIRA).  We have been puzzled today if there is already a best practice of someone, how to map in JIRA TC states on mapping JIRA issue into their specification. Is there any good practice from other groups in a centralised place? I only stumbled over a very basic presentation file (1,34MB) . I have attached the files that I have and hope they are helpful. We do need better documentation on the topic but these do go over basics.  Great! Rob's notes alone are already summarize the way we did it for before. Thanks for the information, Chet! Enjoy your public holiday! Svante   Thanks in advance for your help, Chet! Sure. Again, if you are not getting notifications from JIRA please let me know.  Hereby done :)  /chet   Svante ? -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   ?

Ok - I will look into this today.  /chet On Tue, Jul 4, 2017 at 6:03 AM, Svante Schubert < svante.schubert@gmail.com > wrote: Hello Chet, thanks for your quick reply. Answers below. 2017-07-03 19:41 GMT+02:00 Chet Ensign < chet.ensign@oasis-open.org > : Svante -  On Mon, Jul 3, 2017 at 10:40 AM, Svante Schubert < svante.schubert@gmail.com > wrote: we were running into some JIRA related questions on our last TC call, where you might assist us: We would love to have a notification on the OASIS ODF TC list whenever one of us has been editing an ODF TC related JIRA issue. Reason: We are sometimes surprised that someone worked on a JIRA issue and always explicitly writing to the list that we worked on JIRA seems awkward, right? You should be getting email notifications now. Do you not? If that is the case, I will have to debug the set up to fix whatever is wrong.    As Michael already mentioned there is no update on the list. I worked on an issue yesterday and there is echo on the list: https://lists.oasis-open.org/ archives/office/201707/ maillist.html We would love to have some enhanced JIRA editing functionality, e.g. some of us using JIRA in their projects with the WikiRenderer .  For instance, our new proposal on the this JIRA issue is quite hard to read in plain old text . I will have to find out how much we can do here. I believe I looked into this last year and found that enhancing the interface would require licensing some add-on modules. But I will check again to be sure.    For Michael a whitespace-stable text would be sufficient, I thought a Monospace (or Fixed Font) will do it and offer text highlighting as well. I am currently sending mails to the list and reference from the JIRA issue to them. By this, I got HTML can attach documents (strange that this has been disabled as well in JIRA).  We have been puzzled today if there is already a best practice of someone, how to map in JIRA TC states on mapping JIRA issue into their specification. Is there any good practice from other groups in a centralised place? I only stumbled over a very basic presentation file (1,34MB) . I have attached the files that I have and hope they are helpful. We do need better documentation on the topic but these do go over basics.  Great! Rob's notes alone are already summarize the way we did it for before. Thanks for the information, Chet! Enjoy your public holiday! Svante   Thanks in advance for your help, Chet! Sure. Again, if you are not getting notifications from JIRA please let me know.  Hereby done :)  /chet   Svante ? -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   ? -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 

Hi Svante,  Apologies for my delay getting back to you...  On Tue, Jul 4, 2017 at 6:03 AM, Svante Schubert < svante.schubert@gmail.com > wrote: Hello Chet, thanks for your quick reply. Answers below. 2017-07-03 19:41 GMT+02:00 Chet Ensign < chet.ensign@oasis-open.org > : Svante -  On Mon, Jul 3, 2017 at 10:40 AM, Svante Schubert < svante.schubert@gmail.com > wrote: we were running into some JIRA related questions on our last TC call, where you might assist us: We would love to have a notification on the OASIS ODF TC list whenever one of us has been editing an ODF TC related JIRA issue. Reason: We are sometimes surprised that someone worked on a JIRA issue and always explicitly writing to the list that we worked on JIRA seems awkward, right? You should be getting email notifications now. Do you not? If that is the case, I will have to debug the set up to fix whatever is wrong.    As Michael already mentioned there is no update on the list. I worked on an issue yesterday and there is echo on the list: https://lists.oasis-open.org/ archives/office/201707/ maillist.html <chet: I found that the pseudo-user set up to forward email was marked 'inactive' for some reason. I have changed it to active. It may take some time to propagate across the system. If you don't start getting emails from the JIRA in a day or so, please let me know so that I can explore further.   We would love to have some enhanced JIRA editing functionality, e.g. some of us using JIRA in their projects with the WikiRenderer .  For instance, our new proposal on the this JIRA issue is quite hard to read in plain old text . I will have to find out how much we can do here. I believe I looked into this last year and found that enhancing the interface would require licensing some add-on modules. But I will check again to be sure.    For Michael a whitespace-stable text would be sufficient, I thought a Monospace (or Fixed Font) will do it and offer text highlighting as well. I am currently sending mails to the list and reference from the JIRA issue to them. By this, I got HTML can attach documents (strange that this has been disabled as well in JIRA).  <chet: we are upgrading systems over the next part of the year. I will see what we can work into the new configuration. Meanwhile, I will check to see if there is a setting we can change that affects the white space handling. I've noticed that myself.    We have been puzzled today if there is already a best practice of someone, how to map in JIRA TC states on mapping JIRA issue into their specification. Is there any good practice from other groups in a centralised place? I only stumbled over a very basic presentation file (1,34MB) . I have attached the files that I have and hope they are helpful. We do need better documentation on the topic but these do go over basics.  Great! Rob's notes alone are already summarize the way we did it for before. Thanks for the information, Chet! Enjoy your public holiday! Svante   Thanks in advance for your help, Chet! Sure. Again, if you are not getting notifications from JIRA please let me know.  Hereby done :)  /chet   Svante ? -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   ? -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 

Hi Svante, hi Michael,  I followed up on the JIRA configuration before I left.  On the whitespace layout question, our IT support contact tells me that we can change the default renderer from "plaintext" to "wiki markdown" which would allow using the "{code}" and "{noformat}" codes as Michael suggested. However this is a universal setting and will affect the display of all the existing content in JIRA. Characters like # or * that are already in comment text could cause expected formatting errors. As a result, we can't do that.  Document attachment was also disabled to conserve space. We would need to license more disc storage area.  Did you start receiving email from JIRA?  Best,  /chet   On Tue, Aug 15, 2017 at 2:55 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi Svante,  Apologies for my delay getting back to you...  On Tue, Jul 4, 2017 at 6:03 AM, Svante Schubert < svante.schubert@gmail.com > wrote: Hello Chet, thanks for your quick reply. Answers below. 2017-07-03 19:41 GMT+02:00 Chet Ensign < chet.ensign@oasis-open.org > : Svante -  On Mon, Jul 3, 2017 at 10:40 AM, Svante Schubert < svante.schubert@gmail.com > wrote: we were running into some JIRA related questions on our last TC call, where you might assist us: We would love to have a notification on the OASIS ODF TC list whenever one of us has been editing an ODF TC related JIRA issue. Reason: We are sometimes surprised that someone worked on a JIRA issue and always explicitly writing to the list that we worked on JIRA seems awkward, right? You should be getting email notifications now. Do you not? If that is the case, I will have to debug the set up to fix whatever is wrong.    As Michael already mentioned there is no update on the list. I worked on an issue yesterday and there is echo on the list: https://lists.oasis-open.org/a rchives/office/201707/maillist .html <chet: I found that the pseudo-user set up to forward email was marked 'inactive' for some reason. I have changed it to active. It may take some time to propagate across the system. If you don't start getting emails from the JIRA in a day or so, please let me know so that I can explore further.   We would love to have some enhanced JIRA editing functionality, e.g. some of us using JIRA in their projects with the WikiRenderer .  For instance, our new proposal on the this JIRA issue is quite hard to read in plain old text . I will have to find out how much we can do here. I believe I looked into this last year and found that enhancing the interface would require licensing some add-on modules. But I will check again to be sure.    For Michael a whitespace-stable text would be sufficient, I thought a Monospace (or Fixed Font) will do it and offer text highlighting as well. I am currently sending mails to the list and reference from the JIRA issue to them. By this, I got HTML can attach documents (strange that this has been disabled as well in JIRA).  <chet: we are upgrading systems over the next part of the year. I will see what we can work into the new configuration. Meanwhile, I will check to see if there is a setting we can change that affects the white space handling. I've noticed that myself.    We have been puzzled today if there is already a best practice of someone, how to map in JIRA TC states on mapping JIRA issue into their specification. Is there any good practice from other groups in a centralised place? I only stumbled over a very basic presentation file (1,34MB) . I have attached the files that I have and hope they are helpful. We do need better documentation on the topic but these do go over basics.  Great! Rob's notes alone are already summarize the way we did it for before. Thanks for the information, Chet! Enjoy your public holiday! Svante   Thanks in advance for your help, Chet! Sure. Again, if you are not getting notifications from JIRA please let me know.  Hereby done :)  /chet   Svante ? -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   ? -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 

Hello Chet Thank you for your help and sorry for the late response due to vacation time. Yes, the JIRA notification is working! Looking at the latest JIRA issues of our TC: https://issues.oasis-open.org/ secure/Dashboard.jspa? selectPageId=10270 all latest JIRA changes can be found at notifications in the email archive: https://lists.oasis-open.org/ archives/office/201708/ maillist.html and additionally found in my inbox. Regards, Svante ? 2017-08-22 21:29 GMT+02:00 Chet Ensign < chet.ensign@oasis-open.org > : Hi Svante, hi Michael,  I followed up on the JIRA configuration before I left.  On the whitespace layout question, our IT support contact tells me that we can change the default renderer from "plaintext" to "wiki markdown" which would allow using the "{code}" and "{noformat}" codes as Michael suggested. However this is a universal setting and will affect the display of all the existing content in JIRA. Characters like # or * that are already in comment text could cause expected formatting errors. As a result, we can't do that.  Document attachment was also disabled to conserve space. We would need to license more disc storage area.  Did you start receiving email from JIRA?  Best,  /chet   On Tue, Aug 15, 2017 at 2:55 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi Svante,  Apologies for my delay getting back to you...  On Tue, Jul 4, 2017 at 6:03 AM, Svante Schubert < svante.schubert@gmail.com > wrote: Hello Chet, thanks for your quick reply. Answers below. 2017-07-03 19:41 GMT+02:00 Chet Ensign < chet.ensign@oasis-open.org > : Svante -  On Mon, Jul 3, 2017 at 10:40 AM, Svante Schubert < svante.schubert@gmail.com > wrote: we were running into some JIRA related questions on our last TC call, where you might assist us: We would love to have a notification on the OASIS ODF TC list whenever one of us has been editing an ODF TC related JIRA issue. Reason: We are sometimes surprised that someone worked on a JIRA issue and always explicitly writing to the list that we worked on JIRA seems awkward, right? You should be getting email notifications now. Do you not? If that is the case, I will have to debug the set up to fix whatever is wrong.    As Michael already mentioned there is no update on the list. I worked on an issue yesterday and there is echo on the list: https://lists.oasis-open.org/a rchives/office/201707/maillist .html <chet: I found that the pseudo-user set up to forward email was marked 'inactive' for some reason. I have changed it to active. It may take some time to propagate across the system. If you don't start getting emails from the JIRA in a day or so, please let me know so that I can explore further.   We would love to have some enhanced JIRA editing functionality, e.g. some of us using JIRA in their projects with the WikiRenderer .  For instance, our new proposal on the this JIRA issue is quite hard to read in plain old text . I will have to find out how much we can do here. I believe I looked into this last year and found that enhancing the interface would require licensing some add-on modules. But I will check again to be sure.    For Michael a whitespace-stable text would be sufficient, I thought a Monospace (or Fixed Font) will do it and offer text highlighting as well. I am currently sending mails to the list and reference from the JIRA issue to them. By this, I got HTML can attach documents (strange that this has been disabled as well in JIRA).  <chet: we are upgrading systems over the next part of the year. I will see what we can work into the new configuration. Meanwhile, I will check to see if there is a setting we can change that affects the white space handling. I've noticed that myself.    We have been puzzled today if there is already a best practice of someone, how to map in JIRA TC states on mapping JIRA issue into their specification. Is there any good practice from other groups in a centralised place? I only stumbled over a very basic presentation file (1,34MB) . I have attached the files that I have and hope they are helpful. We do need better documentation on the topic but these do go over basics.  Great! Rob's notes alone are already summarize the way we did it for before. Thanks for the information, Chet! Enjoy your public holiday! Svante   Thanks in advance for your help, Chet! Sure. Again, if you are not getting notifications from JIRA please let me know.  Hereby done :)  /chet   Svante ? -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   ? -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393