Sometimes an issue can't be resolved until someone else does something, or until some event occurs. Is there an add-on for trac that adds a field for these situations?
I use a needinfo keyword for such issues.
Look at AdvancedTicketWrokflowPlugin on trac-hacks. You can use set_owner_to_previous and set_status_to_previous to implement a needinfo state in your ticket workflow. In fact, a needinfo action is the example given on that page.
Disclosure: I wrote the AdvancedTicketWorkflowPlugin and am a Trac developer.
Have you seen the MasterTickets plugin? It adds a "blocked by" field, which is the equivalent of "waiting on". This is for dependencies between bugs, where Bug 101 can't be solved until Bug 102 is.
Related
The problem I face is getting error in flutter plugin, and I have no solution. So I decide to edit some code in plugin, Am I right or wrong for that solution?
Any idea please ?
Thanks.
The answer is Yes.
Yes, you can fork that repo, edit the code according to your requirements.
And then, you have two options
1) Raise the Pull Request and wait till it gets merged or
2) Directly use your updated plugin code
Here is the reference link which will help you to use the updated plugin code as a dependancy.
Yes, definitely you can modify plugin as you want unless and until you can not solve errors without changing it.
I also once change rating plugin to get desire ui in my code.
I am trying to test ODL-SDNiApp and found it not updated since Helium on this page https://wiki.opendaylight.org/view/ODL-SDNiApp:User_Guide. So, is it still supported by Opendaylight? if not, please list me some useful tools or methods for inter SDN controller communication.
Thanks.
According to the project page https://wiki.opendaylight.org/view/ODL-SDNi_App:Main, it last participated in the Boron release but it doesn't look like it's been active since. You can try the project mailing list or contact the listed committers. If it is inactive as it appears, perhaps you might want to try to reboot it.
For a few days, the cloning of issues does not work anyway. I verified my permission scheme, and concerned users, can both create/modify issues, and modify reporters... but it still does not work.
The only change I made is the use of jira.permission.edit.user permission on each JIRA status in my workflow. In my permission scheme, I allowed users to modify users in general, but in my Workflow, using jira.permission.edit.users, I restricted this right for all status since the 2nd status... is that a problem ? do I have to allow cloning issue using any properties on each status ? anything else ?
I suceed to clone an issue... but the clone of my issue is my issue itself with original summary even I specified another one... Anyone has an idea ?
Any help greatly appreciated,
Thanks a lot,
Christophe
Those workflow properties are not particularly well documented. I'd use the permission scheme instead if you can
I configured that jira-users group members can create issues.
And I want to give edit permission to jira-users but only if the issue hasnot a work log in it
Is this possible in JIRA 4.4.x
Thanks
So you can only edit an issue if work hasn't started on it? Tricky. I think I'd end up editing system-issueoperations-plugin.xml and changing the condition elements to add a new condition. The new condition would be a custom condition that checked whether the issue has at least one work log.
You can change issue permissions so that only assignee can edit this issue. So when developer starts work on the issue he assigns himself to this issue and only he can edit it.
Documentation is here - http://confluence.atlassian.com/display/JIRA044/Managing+Project+Permissions
Does anybody have any idea if there exists a demo of a Kohana admin system? (i am thinking at one admin system like Django has one). I am building an online store, and i need a quick way to manage the products inside it. Is there any chance for me to be able to use the Kohana admin system in order to perform this task?
thanks!
i don't know any kohana admin.
the kohana auth will help you to create a security log-in but kohana don't have any pre-builded admin or scaffold.
The cause of kohana don't have any scaffold system or admin is because you will spend more time changing or adapting the admin/scaffold to your needs than do it from zero.
Kohana give you very very impressive tools to build and validate the forms.
If you read the docs carefully and you understand the docs you can program your own admin in less than half an our i guarantee you
A few months ago I was looking for something exactly what you are asking about. I was unable to find a finished product but I found many pieces. I have since been glueing them together as I see fit into the night. The project is quite a buggy mess right now but it works for my purposes. Once I get it in better shape I planned on posting it to my website or maybe github if I ever figure it out that is...
Lately however my job has gotten a bit stricter in regards to coming in early... so I can't code away into the night like I used to. Also, the last component: jQuery mobile UI is still in Alpha 3 so I'm in no major rush either...
My main questions are...
The following are the components it utilizes, will those work with your project?
If 1 == true... and this is for a potential project when would you need/like this module by?
Jelly -->
https://github.com/jonathangeiger/kohana-jelly
Formo -->
https://github.com/bmidget/kohana-formo
Formo-Jelly -->
https://github.com/bmidget/kohana-formo-jelly
Jelly-Auth -->
https://github.com/raeldc/jelly-auth
Jelly-Auth-Demo -->
https://github.com/rob/jelly-auth-demo
A neat admin template style -->
http://mathew-davies.co.uk/2010/03/13/free-admin-template.html
A x12 Grid from -->
http://960.gs/
jQuery Mobile UI Elements -->
http://jquerymobile.com/
Posted as answer instead of a message, just in case others are interested... Gauging the amount of interest will likely determine the amount of evening time sacrificed.
Kohana does not have a magical admin system like Django.