Projects: Issueshttp://projects.andriylesyuk.com/http://projects.andriylesyuk.com/plugin_assets/andriy_lesyuk/images/s-andy.ico2012-06-26T13:59:32ZProjects
Redmine SCM Creator (+Github) - Feature #2075 (Open): Make an option to fully automate repository creatio...http://projects.andriylesyuk.com/issues/20752012-06-26T13:59:32ZHumberto Anjos
<p>Here’s my situation: I need a SourceForge-like solution for internal use in my company, and Redmine seems like the best option. I need to create repositories only through Redmine, so this plugin fell like a glove <span class="wiking smiley smiley-smiley" title=":)"></span> Thing is, the URL field is fully editable, so users can create repos anywhere on the server <span class="wiking smiley smiley-sad" title=":("></span></p>
So my current options now are:
<ul>
<li>stick to Redmine 1.3 and SCM Creator 0.3; or</li>
<li>migrate to Redmine 2, SCM Creator 0.4, use the <a href="http://projects.andriylesyuk.com/projects/scm-creator/wiki/Common-configuration-scenarios#Force-repository-creation-for-all-projects" class="external">Force repository creation for all projects</a> configuration and limit repos to one per project (<code>max_repos: 1</code>), so the user never gets the option of editing the URL.</li>
</ul>
<p>The best solution (for me) would be for the URL field to be non-editable, and for the URL to be fully determined by the project name, the path in <code>scm.yml</code> and the repository identifier. So, for a path <code>/var/lib/svn</code>, a project <code>test</code> and an repository <code>main</code>, the repo’s full URL would be <code>file:///var/lib/svn/test/main</code>.</p>
<p>Of course, Redmine-based authentication should still work (it seems like a simple matter, but I don’t know if there’s any hidden surprises...).</p> WikiNG - Feature #1977 (Open): Conditional macro for users & groupshttp://projects.andriylesyuk.com/issues/19772012-02-16T08:43:48ZДмитрий Салашник
<p>I think something like <br /><pre>
{{visible for some_user1, some_user2, group1, group2, role1, role2 }}
This text is invisible for other peoples :)
{{visible}}
</pre></p>
<p>This is really required feature, it allow’s include some technical comments for developers <span class="wiking smiley smiley-smiley" title=":)"></span> or something else</p> SCM Creator (+Github) - Feature #1793 (Incomplete): Allow the creation of non-local repositories http://projects.andriylesyuk.com/issues/17932011-06-17T17:22:15ZStefanos Kariotidis
<p>It would be nice if the plugin could create non-local repositories like reposman.rb.<br />I don’t know how difficult this may be but if is doable this plugin will shine in contrast to<br />reposman.rb. I say this because i find SCM Creator very delicate, robust and better polished addition to Redmine.</p>
<p>Regards, Stef</p> Orangutan - Feature #1619 (Open): Avatarhttp://projects.andriylesyuk.com/issues/16192011-02-03T13:20:32ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Currently the only method to change Orangutan’s avatar is to use another Jabber client to upload it.</p>
<p>I guess it’s easy to support this! A new configuration option can be added:<br /><pre>
jabber.avatar = /path/to/avatar.png
</pre></p>
<p>Then on every start Orangutan can ensure the right avatar is set...</p> Orangutan - Enhancement #1618 (Open): Support subrequests in single request messagehttp://projects.andriylesyuk.com/issues/16182011-02-03T13:13:51ZAndriy Lesyuks-andy@andriylesyuk.com
<p>One of the limitations of Orangutan is that he mades currently a single change to Redmine. While in Redmine you can change several properties...</p>
Let me explain... Check this scenario:
<ol>
<li>User tells “100% done”, Orangutan saves this</li>
<li>Orangutan asks if user wants to close the issue</li>
<li>User agrees, Orangutan changes status + sets due date (in separate context)</li>
</ol>
What we will have? We will have three journals:
<ol>
<li>Changed done ratio to 100%</li>
<li>Changed status to Closed</li>
<li>Changed due date to XX/XX/XXXX</li>
</ol>
<p>The last two journals will have exactly the same date of creation!.. This can end up with many little journals!</p>
One of the possible solution is (when posting change) to "add" changes to the previous journal. But the issue with this solution are:
<ul>
<li>Some user will already get notifications about the journal without new change</li>
<li>The change date won’t be accurate</li>
</ul>
So the another (and better) solution is:
<ul>
<li>Support subrequests in user messages like:<br /><pre>
User: #1617 is 100% done, close #1617 and change due date to today
</pre><br />This should be the same as:<br /><pre>
User: #1617 is 100% done
User: Close #1617
User: Change due of #1617 date to today
</pre><br />But this should only create a single journal.</li>
<li>Postpone commit to the end of message handling.<br />That is if some another context is changing something on some event in its event handler it will be added to the same journal.</li>
</ul>
<p>P.S. Subrequests can be of completely different types, e.g.:<br /><pre>
User: #1617 is Closed and I am free now
</pre></p> Orangutan::Redmine - Enhancement #1616 (Open): Redmine notification for changes made in Orangutanhttp://projects.andriylesyuk.com/issues/16162011-02-03T12:15:15ZAndriy Lesyuks-andy@andriylesyuk.com
<p>When a change is made in Redmine - both Orangutan and Redmine will notify users about a change. But when a change is made in Orangutan - only Orangutan will know about it. In some way this <strong>breaks</strong> proper behaviour of Redmine. And this should be fixed (I guess users won’t be happy if they miss something).</p>
<p>Possible solution is to create special Redmine REST API for notifications. When a change is made Orangutan will call some “function” to let Redmine know about the change. Then Redmine will emulate the change and notify everyone (we should ensure that Orangutan won’t get these notifications or will be able to recognize them).</p> Orangutan - Enhancement #974 (Open): Rich text/formatting supporthttp://projects.andriylesyuk.com/issues/9742010-10-12T17:25:15ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Many times I thought it would be great if text written by Orangutan would be “colorized”... This way we can highlight urgent issues, highlight important part of messages etc.</p>
<p>Preliminary research if it is possible did not give any results. Looks like XMPP library used does not support this (rich text messages). But... Should it stop us? <span class="wiking smiley smiley-smiley" title=":)"></span> There is always possibility to improve things even if this is third party lib...</p>
<p>Any help (with research e.g.) would be appreciated!</p> Orangutan::Redmine - Feature #969 (Open): Editing commentshttp://projects.andriylesyuk.com/issues/9692010-10-11T20:56:27ZAndriy Lesyuks-andy@andriylesyuk.com
<p>It was requested to add editing of comments. Not sure how needed this feature woul be. Please vote...</p>
<p>The main question is how to implement this... It seems like these should be queries like the following:</p>
<pre>
You: Edit comment #2 of #146
You: Edit last comment of #146
</pre>
<p>Currently comments (during output) are numbered taking into account only their position in history. Unlike Orangutan Redmine numbers not just comments but changes (journals). I’m afraid that there can be a confusion - saying a user sees comments he want to change in Redmine having number <a class="issue tracker-2 status-5 priority-4 priority-low2 closed" title="User should be able to see his configuration (Closed)" href="http://projects.andriylesyuk.com/issues/15">#15</a>. He can assume that this number is the same for Orangutan. So perhaps numbering in Oranggutan should be changed to be identical to Redmine.</p> Orangutan - Feature #558 (Open): Jokes contexthttp://projects.andriylesyuk.com/issues/5582010-06-15T20:52:22ZOleh Demyanyukolkobg@gmail.com
<p>tell redmine 'joke’ and he print something like fortune command form linux...</p> Orangutan::Redmine - Feature #230 (Open): Starting task/time entry and new issue at the same timehttp://projects.andriylesyuk.com/issues/2302010-04-16T00:31:36ZAndriy Lesyuks-andy@andriylesyuk.com
<p>In the testing phase most of their time developers fix bugs. Mostly these are small bugs. So it can be a headache to add issues to Redmine and then to add time logs using Orangutan...</p>
<p>The idea is to create a context which would allow to create issue and time log with one “command”.</p>
<p>The syntax can be:</p>
<pre>
User: Fixing new issue: Dialog is shown incorrectly [high]
</pre> Orangutan::Redmine - Feature #184 (Open): Notifying about due date and hourshttp://projects.andriylesyuk.com/issues/1842010-04-01T19:39:49ZAndriy Lesyuks-andy@andriylesyuk.com
<p>It is important to receive a notification when due date came or when hours “limit” is over. The corresponding contexts should use scheduler.</p> Orangutan::Redmine - Feature #180 (Open): Issue status changinghttp://projects.andriylesyuk.com/issues/1802010-04-01T18:58:12ZAndriy Lesyuks-andy@andriylesyuk.com
<p>As far as most of the work with an issue is going to be done using Orangutan it would be very useful to be able to change issue status using some special context.</p>
<p>Some samples and ideas:</p>
<p>User: <a class="issue tracker-2 status-7 priority-6 priority-high2" title="Reminder, organizer and scheduler (Open)" href="http://projects.andriylesyuk.com/issues/128">#128</a> is <strong>new</strong><br />User: <strong>Resolve</strong> <a class="issue tracker-2 status-7 priority-6 priority-high2" title="Reminder, organizer and scheduler (Open)" href="http://projects.andriylesyuk.com/issues/128">#128</a><br />User: <strong>Close</strong> <a class="issue tracker-2 status-7 priority-6 priority-high2" title="Reminder, organizer and scheduler (Open)" href="http://projects.andriylesyuk.com/issues/128">#128</a></p>
<p>In addition the context should be called when issue is changed to be 100% done (e.g.). Of course, it should ask for confirmation:</p>
<pre>
Orangutan: So should I change its status to "Closed"?
User: Yes
Orangutan: Ok.
</pre> Orangutan::Redmine - Feature #170 (Open): Issue creationhttp://projects.andriylesyuk.com/issues/1702010-03-31T18:31:29ZAndriy Lesyuks-andy@andriylesyuk.com
<p>It would be very useful to have a contexts allowing to create issue. These contexts should be similar to bug tracking ones (now removed). The contexts should allow to create an issue by one command. Possibly some contexts should allow to modify existing issues. Which dialogs/requests to use for creating issues is to be determined (suggestions are welcome).</p> Orangutan - Feature #128 (Open): Reminder, organizer and schedulerhttp://projects.andriylesyuk.com/issues/1282010-03-09T17:52:50ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Saying you have something you must do before meeting. So it would be great to create a reminder which would remind you to do this something. The reminder should, of course, support a date... Format can be something like: “Remind me to <do something> on Monday”. This is an optional feature request. Just an idea.</p> Orangutan::Redmine - Feature #124 (Open): Let users specify what they did during a break by answe...http://projects.andriylesyuk.com/issues/1242010-03-09T17:47:14ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Saying I’m working on something and suddenly my manager asks me to attend a meeting. Saying the meeting lasts for an hour. When I get back Orangutan asks me if he should record a break. That’s fine! But it would be cool if I could answer something like: “Yes... I had a meeting with my manager.”. And he would add this as a task.</p>