Default detailed description and Time Tracking
Hey there,
today my company announced that we want to go agile. We choice the way of Scrum and we saw that Gemini is a self -called agile managment tool.
I got now some question and would be happy if you have the answers :
We just install to Gemini local to see if it fit our desire. We saw the classic simple issue create mask.
Is it possible to define default text into the detailed description like this ? :
http://img4.abload.de/img/defaultdetaileddescripi9z5.jpg
That would be awesome.
Also another question we got is, that we want to make a "Backlog" project. This is where all the task for the developers are defined.
This task should only be once posted. I mean for example we got project "Wolverine" and project "Kryptonite". Developer Tom must add a method to the component "Wolverines Heart" in the project "Wolverine". Developer Tim must fix a bug in the component "Krytonite power" in the project "Kryptonite".
So the two post there task into the Backlog project and link them to the specific project. Is something like this possible ?
See following illustration for better understanding :
http://img4.abload.de/img/projectsdyyt.jpg
Thanks again :D
Jabba
· 1 |
|
Tuesday, October 6, 2009, 5:05:57 PM |
0
|
It is possible to set the default text, but it will apply to all of the rich text editors (description, comment etc...). Why not use required custom fields for this? |
||||
|
0
|
Hey first thanks for your answer. We are now looking into Gemini to figure out how to use it right. In our last Issue Tracking System our Point-of-View was Project Managment like. For every software one project. We offer special versions for every customer and so our database was just over bloated. We saw that Gemini is given us such thing as project labels. But we know that soon or later it will become again like the old system. We just take a peek look at the Gemini demo at your site and saw that you only have one project each finished software. We dont know how to handle this with our philosphy. We could make just one project for each project. But there are so much difficults between customer versions. Also we want the dialog with the costumer. We can create a global group "costumer" who only can see there own issues, but there can also see all projects right ? Maybe there is something like a best practicse for project/software managment with Gemini. A costum detail descritption field would do it. But can we disable the old detail description field ? Thanks |
||||
|
0
|
Here are some suggestions/thoughts... If you use one project per software product then you could use Versions for per client "boxing": each client's issues will get rolled up into a Version specific to a client. But, you have to careful on version labels/numbers/description as when a client logs in, they can see ONLY their OWN issues, BUT the versions filter will show all versions (even though some of them are for other clients). Yes, you can do a Project per version and yes this may result in lots of projects. As for hiding/defaulting the detailed description field: Locate control in the "Controls\IssuesUC.ascx" file and amend the following two properties: Text="Field Not Used" Visible="false" |
||||
|
0
|
Am I correct, that when I change the value to false of visible it will effect in all projects ? We just need it for our backlog project. My thoughts about control our project with Gemini is now going into the Scheme direction. For example I got two softwares. The customer only see his/her issues and so on. But what a project groups all about ? For me there make no sense. Right now I am playing with the Field Visibility Schemes but there is something I am doing wrong. I set all options on true and visible for Everyone. Than i saved it and wanted to create an issue but there wasn´t all option like Work estimate. I was really confused till I set my User Account into the developer global group. After that I saw more fields. What am I doing wrong ? |
||||
|
0
|
Yes, it will not be visible for all projects. |
||||
|
0
|
Hey Mark, thanks for your help. I was not talking about "project labels" but rather about "project groups" :-). Also the visiblilty problem is still here. I just made some screenshots to show you what I mean. On the last screen I just added my user to the developer global group : http://img6.abload.de/img/146f6.jpg http://img6.abload.de/img/2p6hc.jpg http://img6.abload.de/img/3a6m5.jpg http://img6.abload.de/img/486ld.jpg
Thanks again for the help. |
||||
|
0
|
You need to set the visibility scheme to the issue type(s). |
||||
|
0
|
Hello, is it possible to create a sub issue of a sub issue ? I tried it 3 time and it didn´t worked out for me. Or am I doing something wrong ? |
||||
|
0
|
No, at the moment we only allow one level (a sub issue can not be a parent issue). |
||||
|
0
|
Hey, we need default detailed description text in one specific project. It this now possible in Gemini ? Or must we still do the workaround with the customfield ? Thanks |
||||
|
0
|
This is still not possible. |
||||
|