A forum for technical support discussion related to Fogbugz.
So there are two kinds of releases...
Ones specific to a project and those that are assignable to any project.
I created a couple releases in as global, since they span project boundaries. But then, when I look at the reports feature of version 6, I see that they are not considered releases suitable for doing any reporting on? Is this a bug, over-sight, or what have I missed?
I then added the identical release to one of the projects' specific releases. I now have the exact same release name in there twice, once as global and once as unique to a project. I intended to delete the global one only to find out.... you can't! I see in the forum here that it's been an issue, but I obviously need a way to delete this redundant release. How would someone even know what to pick?
Am I doing something wrong?
Friday, September 21, 2007
You can make those un-needed global releases in-active, or if they haven't been used at all you could re-perpose them by changing their names and dates.
Ian M. Jones (CaseDetective)
Saturday, September 22, 2007
Okay... because that issue is kind of killer for EBS to even work, IMO. We have a metric ton of projects that break down an uber project. You know, hierarchical projects would really save the day....
Anyway, they have to share releases.... it's the same app at the end of the day. :/
Monday, September 24, 2007
This topic is archived. No further replies will be accepted.Other recent topics