Stefano Mazzocchi wrote: > Ryan Lee wrote: >> unless we can get the JIRA source. > > Well, JIRA is mostly JSPs and we have those, so shouldn't be that hard.
Ah, found something of use. >> A simple grep through the original JIRA files for the phrases 'rowse >> project' and 'reate new' only shows them embedded in .class files. > > which "original" files are you talking about? The ones used to compile JIRA into a deployable application. I was wrong about those, too; those strings are just Java comments. The real strings are buried in .properties files in a language .jar. Once I found that, it became clear that modifying includes/decorators/bodytop.js was the place to go. Unfortunately, JIRA's default behavior when visiting a 'create new issue' page without being logged in is to present you with a screen asking you to first select a project from non-existent UI components (because you don't have permission to see them) - not a request asking you to log in. >> We may want to just write our own starter page that links to relevant >> spots in JIRA and call that the issue tracker homepage. > > that's not a bad idea either. So we can modify JIRA's behavior and strings so 'create new issue' is always displayed and the 'create new issue' page is more informative about what to do next (at least, I think it's possible). Or we can (also?) add a wiki template for creating per-project issues that explains logging in is required before one can effectively use it. -- Ryan Lee [EMAIL PROTECTED] MIT CSAIL Research Staff http://simile.mit.edu/ http://people.csail.mit.edu/ryanlee/ _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
