|
35
28
|
Bug-monkey scripts probably don't qualify as full plug-ins on their own right and probably don't belong in the plug-in gallery, but it would be nice to have a centralized repository of BugMonkey scripts/css where people can share them Since they are essentially just text blocks, I though I'd open a Question on here where people could post their scripts and/or vote on the best ones. Michael: If you had other ideas for another place to do this, please let me know and I'll delete this post. |
|||||
|
|
2
|
Here's what we're currently working on. This is very much a work in progress and we've got a more planned. Some notes:
Here's the code (just the CSS field in BugMonkey):
a.vb{color: #0F5491 !important}
a.uvb{font-weight:bold !important}
#mainArea,#mainAreaContinued{font-size:10pt !important}
.changes{padding: 0 !important}
#idContainer{width: 90% !important}
#www-fogcreek-com-fogbugz,#mainArea{font-family:Arial;}
.buttonbar {width: 100% !important}
div.bugShadowBottom {width: 100% !important; max-width: 79em;}
#bugviewContainer {width: 100% !important}
#bugviewContainer .top .ixBug {width:13em !important}
#bugviewContainer .top .idTitleProjectAndArea {margin-left:13.5em !important}
#bugviewContainer .side {width:13em !important}
#bugviewContainer .bugevents {margin-left:14em !important}
#bugviewContainer .bugevents .bugevent .body textarea { width:99% !important}
#BugFields, #BugMeta {width:100% !important}
div.emailHeaderName {font-family:arial !important; font-size:8pt !important; color:#555 !important;}
div.emailHeaderValue {font-family:arial !important; font-size:8pt !important; color:#555 !important;}
div.emailBody {font-size:10pt !important; padding:12px 10px !important;}
#bugviewContainer .top .row1 {width: 49.3em !important;}
#bugviewContainer .top .row2,
#bugviewContainer .top .row3,
#bugviewContainer .top .rowPlugin {width: 15.5em !important}
#bugviewContainer .top .row2 input,
#bugviewContainer .top .row3 input,
#bugviewContainer .top .rowPlugin input {width: 17em !important}
#bugviewContainer .top .plugins.edit {margin-left:0em !important; clear:left; width:100% !important;}
#bugviewContainer .top .title {font-size:1.5em !important;}
.bugTopItem3 {width: 99% !important}
#bugviewContainer .bugevents .bugevent .summary .action {font-size:10pt !important;}
#bugviewContainer .bugevents .bugevent .changes {font-size:10pt !important;}
#banner {border-top: 2px solid #E0E9F1 !important; border-bottom: 2px solid #E0E9F1 !important; }
.bugs tbody tr td {font-size:12px !important; color:#888 !important; }
.bugs tbody tr td a {text-decoration:none !important; }
.bugs tbody tr td a:hover {text-decoration:underline !important; }
#mainArea #bugGrid .g-r-context td a { color: #999 !important; }
#mainArea #bugGrid .g-r-context td a.dotted { border-bottom: 1px dotted #999 !important;}
|
|||||
|
|
7
|
Here's some sample javascript which can be used to replace text in bug events. I'm currently using this for creating links and replacing long urls with shorter ones within bug events. In this sample there are two objects which I use as a poor man's replacement for hashes:
What these replacements do:
To add more replacements just add a matching pair of aRegExps and aReplacements objects. A couple of notes about this sample:
Here's the sample: Note that you need to edit the below js code to adit/add your keywords and corresponding replacements. |
|||
|
|
|
4
|
I have taken parts of Jake B's CSS code and joined it with our own Bugmonkey CSS code. Fogbugz 7 default look (left) and the look after the redesign (right): Screenshots here: http://img12.imageshack.us/img12/7561/fogbugz.png |
|||
|
|
|
5
|
I posted a simple script to make the Project: Area on the case page into live links. |
|||
|
2
|
I wanted to get the contents of one special article displayed in a panel to the left of every page in a Wiki. The Wiki is a product spec, the special article is where we maintain the table of contents. Not an ideal solution, because the left panel gets cleared/reloaded with every refresh, but... here's what I did: First, I modified that Wiki's template HTML so that there were some new div's with unique id's. The most important ones for this example are an empty container for the table of contents and a container containing only the body of the article. Then I modified the Wiki's template CSS to lay out the new div's (there are most likely many ways to do this nicer). Next, I created the table of contents in a Wiki article (W370 in my case) and added the JavaScript to BugMonkey that would load it. There's also a function to show/hide it. I call it from an onClick attribute in a tag that I put in the HTML template. |
|||
|
|
|
3
|
I posted a script that adds a "Toggle Hierarchies" button to the upper-right corner of the list cases page. Clicking it will collapse/expand all the case hierarchies on the page. |
|||
|
3
|
I posted a script that will help you determine what type of user you're dealing with (Not logged in, Normal, Community, or Administrator) and the user's full name (or "Anonymous" if they're not logged in). |
|||
|
|
|
2
|
I did a script that lets you go into Edit mode by clicking anywhere in the body of a wiki page. This is a feature of TiddlyWiki that was sorely missing IMHO. :) I implemented this as an optional thing, since some of the users didn't want this dbl-click functionality. |
|||
|
5
|
I posted a script that makes the case history text that is generated when you add a subcase (e.g., |
|||
|
|
|
3
|
Add the following CSS to hide the "Send & Close" and "Resolve & Close" buttons when editing a case. (The wording and function of these buttons are confusing to users and more often than not lead to incorrectly-closed cases.) |
|||
|
6
|
In using FogBugz, I noticed that most of the users didn't like seeing the full history of everywhere a bug had been in its storied life. For particularly old bugs, there might be a full page of "Assigned to Peter", "Assigned to Paul", "Assigned to Mary", "Milestone changed to 1.2.3" et cetera. Since people managing the bugs usually needed to see these 'empty edits' and the people fixing bugs only rarely did, I use BugMonkey to hide the 'empty edits'. I use a session cookie to remember the setting. Also, I very rarely need to see the full header of an email. We use email as a method for our support staff to submit information about cases. As such, their email should look more like an edit and less like something else. I've reformatted the email so that the header is togglable (default to off) and the emails look more like edits. If the email is an Out of Office Autoreply, hide it. This will also provide color coding for incoming vs. outgoing emails, so the email chain can be easily scanned for information. Script: |
|||
|
|
|
2
|
I posted a script to auto-create links on the case view page for protocols other than http and https (such as ftp://, file://, telnet://, etc.). |
|||
|
|
|
2
|
Remove "FogBugz: " from of every page, to be browser-tab-friendly - consuming less space |
|||
|
9
|
|
|||||
|
|
2
|
I posted Daniel's script to highlight cases in grid view which are overdue. It can also highlight due today and due tomorrow. |
|||
|
|
|
0
|
Here is a really simple script to alternate the colors for case events on the case detail view. Prompted by this newsgroup question. |
|||
|
|
|
2
|
Links to UNC paths: convert [\unc\path\directory] to proper link: Requires proper configuration of Firefox, to allow intranet links from your FogBugz server: http://kb.mozillazine.org/Links_to_local_pages_don%27t_work [Note: Someone please post Chrome solution, and delete this note] |
|||||
|
|
1
|
I posted a script which gives you the option to convert things in hours format to days/hours/minutes format. |
|||
|
|
|
2
|
Daniel posted a script to hide bugevents you have already seen. |
|||
|
|
|
0
|
Here's a script to hide all Backlog change entries: |
|||
|
|
|
1
|
I posted a script that lets you make custom fields always visible or always hidden on a per-project basis. |
|||
|
|
|
1
|
I posted a script that saves drafts of emails and bug edits as you type (and allows you to restore them if your browser crashes or you accidentally close your window) |
|||
|
|
|
0
|
If you want all your case titles on the single bug view page to contain the case number pre-pended ala FogBugz 6 (perhaps for easy copy and paste): |
|||
|
|
|
0
|
I posted a script that adds the "Favorites" star to the popup that appears when you hover over a case ID. |
|||
|
|
|
1
|
I posted a script that shows the size of files that you are attaching to a case event, and gives a visual warning if the file size exceeds the maximum allowed attachment size. |
|||
|
|
|
1
|
I wanted to add up a custom field called "Story Points" and also total the "Estimate (original)" column. Here's a script that does this, it is adaptable to summing up other columns as well. Many thanks to others who posted scripts, I have incorporated (i.e. stolen) many ideas! |
|||
|
|
|
0
|
Some Kanban plugin mods to make it play nice in FB8: |
|||
|
|
|
0
|
I posted a script to easily toggle the visibility of all quoted texts in e-mails. When searching a long case for something you just know is there but you cannot find it, it might be hidden in a 'quote'. One click now expands them all! |
|||
|
|
|
2
|
Here is a short script I wrote that adds an "Edit" link next to each case in the case list/grid. This allows to quickly open several tests in a new window, already in edit mode. |
|||
|
6
|
I've been able to create a custom menu that looks and performs exactly like the native menus in FogBugz (Filters, Schedules, Wiki, etc)
http://fogbugz.stackexchange.com/questions/6471/how-to-create-a-custom-menu-in-the-menu-bar |
|||
|
|
