You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2011/09/03 19:18:09 UTC
[jira] [Created] (OOZIE-44) Oozie JIRA changes that'd be favorable
Oozie JIRA changes that'd be favorable
--------------------------------------
Key: OOZIE-44
URL: https://issues.apache.org/jira/browse/OOZIE-44
Project: Oozie
Issue Type: Improvement
Reporter: Harsh J
Priority: Trivial
None of this is urgent to do at the moment (given all the work you're already going through -- let me know if I can help in any way too!). But am just compiling some notes here to make the Oozie jira work/act more like the other ecosystem elements:
- Enable formatting in comments. Right now tags like {code}, (-), etc. do not work. These are useful in filing reports or talking in general.
- Limit down issue types in this JIRA instance. HDFS, for example, has just Bug, Task, Improvement, New Feature, Wish types. OOZIE seems to have a load of things.
(Will add more notes as a comment as I notice them while contributing things)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-44) Oozie JIRA changes that'd be
favorable
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097666#comment-13097666 ]
Roman Shaposhnik commented on OOZIE-44:
---------------------------------------
not sure about the rest, but { noformat } seems to
{noformat}
work for me
{noformat}
> Oozie JIRA changes that'd be favorable
> --------------------------------------
>
> Key: OOZIE-44
> URL: https://issues.apache.org/jira/browse/OOZIE-44
> Project: Oozie
> Issue Type: Improvement
> Reporter: Harsh J
> Priority: Trivial
>
> None of this is urgent to do at the moment (given all the work you're already going through -- let me know if I can help in any way too!). But am just compiling some notes here to make the Oozie jira work/act more like the other ecosystem elements:
> - Enable formatting in comments. Right now tags like {code}, (-), etc. do not work. These are useful in filing reports or talking in general.
> - Limit down issue types in this JIRA instance. HDFS, for example, has just Bug, Task, Improvement, New Feature, Wish types. OOZIE seems to have a load of things.
> (Will add more notes as a comment as I notice them while contributing things)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-44) Oozie JIRA changes that'd be
favorable
Posted by "Harsh J (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123594#comment-13123594 ]
Harsh J commented on OOZIE-44:
------------------------------
A requester can resolve their issue but can't choose a fix version, etc.
I wonder if this JIRA config can be stolen out from HADOOP's? That may very well resolve this issue :)
> Oozie JIRA changes that'd be favorable
> --------------------------------------
>
> Key: OOZIE-44
> URL: https://issues.apache.org/jira/browse/OOZIE-44
> Project: Oozie
> Issue Type: Improvement
> Reporter: Harsh J
> Priority: Trivial
>
> None of this is urgent to do at the moment (given all the work you're already going through -- let me know if I can help in any way too!). But am just compiling some notes here to make the Oozie jira work/act more like the other ecosystem elements:
> - Enable formatting in comments. Right now tags like {code}, (-), etc. do not work. These are useful in filing reports or talking in general.
> - Limit down issue types in this JIRA instance. HDFS, for example, has just Bug, Task, Improvement, New Feature, Wish types. OOZIE seems to have a load of things.
> (Will add more notes as a comment as I notice them while contributing things)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OOZIE-44) Oozie JIRA changes that'd be favorable
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated OOZIE-44:
----------------------------------
Comment: was deleted
(was: not sure about the rest, but { noformat } seems to
{noformat}
work for me
{noformat}
)
> Oozie JIRA changes that'd be favorable
> --------------------------------------
>
> Key: OOZIE-44
> URL: https://issues.apache.org/jira/browse/OOZIE-44
> Project: Oozie
> Issue Type: Improvement
> Reporter: Harsh J
> Priority: Trivial
>
> None of this is urgent to do at the moment (given all the work you're already going through -- let me know if I can help in any way too!). But am just compiling some notes here to make the Oozie jira work/act more like the other ecosystem elements:
> - Enable formatting in comments. Right now tags like {code}, (-), etc. do not work. These are useful in filing reports or talking in general.
> - Limit down issue types in this JIRA instance. HDFS, for example, has just Bug, Task, Improvement, New Feature, Wish types. OOZIE seems to have a load of things.
> (Will add more notes as a comment as I notice them while contributing things)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira