Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




ability to create a recurring issue or task?

web-app

We've been using Gemini for about a year or so now.  It works "good enough" for our software development projects... but for my infrastructure / helpdesk team... it's a little more awkward.

One thing that would be really help both teams would be the ability to create a recurring task/issue (a-la Outlook).  For example, the IT team needs to do a login review on a quarterly basis.  Now, we can go in and create 4 issues for the year, but... you can see where this would be tedious if the frequency was higher (say "weekly").

In Outlook, you have some nice options for setting up a recurring task (but I don't want to use Outlook since that's a person-by-person thing, doesn't have the visibility and tracking and history like Gemini does, etc.).  For example, you can say... set the reocurrance to happen the first Monday of every month, regenerate the task on schedule or when the current task is done, set an end date or let it keep regenerating tasks, etc.


MNoreen
· 1
MNoreen
Replies (4)
helpful
0
not helpful

This is a very good idea that is currently not possible without writing cusotm code usign Gemini web services.

However, we would like to add this and some questions:

It sounds like you would recquire a schedule tab in the create / view issue screen. Inside the schedule tab you'd want the ability to view and define reoccuring creation schedules for the issue.

Questions:

  • Are "future" issues created immedietly when the scheduele is defined or is it created when the date comes?
  • Which issue attributes would you not copy? (status etc...).

Thanks.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Good questions! 

1) When to create the issue?  I'm somewhat ambivalent about it.  The really nice thing would be to have the choice (go ahead and pre-create the issues according to selected scheduling choices) OR only create the next issue after the current one is marked as "completed" or whatever status is chosen to mean as much.

But, if it meant getting it to the table quicker, I'd vote, let it pre-schedule the issues out (perhaps giving the user a choice on how far to let it do so... either by choosing an end date or by a number of occurences). 

 

2) Which attributes to copy or not? That could get tricky indeed.  It seems like the obvious ones to NOT copy would be Resolution, Start Date, any of the time logging fields... fixed for version, also.

 

 

 

 


MNoreen
· 1
MNoreen
helpful
0
not helpful

Makes sense.

Log your issue here:
http://gemini.countersoft.com/Main.aspx

...and lets get this thing done.


Harvey Kandola
· 212
Harvey Kandola
helpful
0
not helpful

Thanks!  I just created an item for it (see GEM-2206).  And that's kinda neat that you use your own product to let users submit requests... :)


MNoreen
· 1
MNoreen