Topic: how do I tell how much memory I use?

Use the “Jump to…” to go to your Account Settings page.

Scroll down and you’ll see a Disk Usage chart that shows you how much you’re currently using.

Topic: commits not being associated to tickets

Should have looked harder.

The original blog post is here:

http://unfuddle.com/blog/2007/7/26/powerful-subversion-commit-messages

Andy

Topic: commits not being associated to tickets

I think you need to put ‘addresses #257’ to associate the changeset.

There are other tags like ‘closes’ as well I think, but I can’t seem to find the documentation for them. Anyone?

Andy

Topic: create links from ticket descriptions to repository

allyforce,

The repository abbreviation is the value you see in parentheses next to the repository name on the repositories tab.

Topic: additional person cannot add value to time tracking

Allyforce,

In order for your users to be able to use time tracking, they much have at least read access on People as well (as time tracking is so interlinked with the concept of people).

Topic: create links from ticket descriptions to repository

allyforce,

You can link to a specific file in the repository browser with the following markup:

source:repo_abbr:/path/to/file

Please note that if there is only one repository associated with the project you do not need to include the repository abbreviation and extra colon. That is only necessary to distinguish multiple repositories.

Topic: Authorization Failed

Allyforce,

There are no issues with Subversion authorization right now. This probably due to some constraints within your account. As such, I would suggest contacting support directly with your account information.

Thanks,

Josh

Topic: attaching images in notebook

When you add the link it’s probably giving you something like

{{foo.png}}

To make that display as an image, just use the image markup which is

![alt text](/path/to/image.png)

So you’ll need something like:

![alt text]({{foo.png}})

Topic: close tickets -- who has ability?

Allyforce,

As you know, in Unfuddle it is certainly possible to restrict a person’s interaction with tickets. Unfuddle currently allows for four levels of ticket interaction:

• No access
• Read only access
• Read and create access
• Manage access

Once the person has been given the ability to “manage” tickets, they have the ability to truly manage tickets, including seeing them through closure.

Thus, the short answer to your question is that, while you can certainly limit a person’s access to tickets—no, you cannot restrict your active development team from closing tickets within Unfuddle.

The long answer is that we stand firmly on the premise that, unless the development team is exceptionally large, the enforcement of permissions through fine-grained systemic controls almost always results in a system that is difficult to use.

In our experience, simply discussing processes with the team ends up being an adequate control. If I had a team member who could not be trusted to follow my instructions to not close tickets, then I would deem that person to be an unreliable team member, i.e. one to whom I would certainly not want to entrust my code.

Topic: formatting in "fixed" tickets

Allyforce,

I believe that you may be talking about the fact that Markdown will render any text that has been indented with at least four lines into a code block. Unfuddle then styles code blocks with a “white square”.

Josh

Topic: close tickets -- who has ability?

Allyforce,

Anyone who has the ability to create a ticket can enter the initial estimate for a ticket. However, once created, only a project administrator has the ability to modify that initial estimate. From the point of creation, non-administrators may only update the “current estimate”. In this way, you can maintain accountability throughout your team.

I hope that helps!

Topic: close tickets -- who has ability?

Allyforce,

Here is a quick overview of permissions in Unfuddle:

None: In every context, none means that the person will not be able to do anything (read, create, etc). The interface will automatically hide any elements related to the context.

Read Only: Allows the person to view items in the given context. In the Messages and Tickets context, “Read Only” will also allow them to comment on the messages or tickets. In the Source context, the person will be able to checkout the repository, but not commit to it.

Create Only: (only in Tickets) This permission does not allow the person to read tickets, however, they are able to create new ones (which they can thereafter not access themselves).

Read and Create: The person is allowed all of the permissions of “Read Only” and they are able to create elements in the given context.

Manage: The person has the ability to read, create and edit an item within the given context. In the case of Messages and Tickets, they are not, however, allowed to edit comments that do not belong to them.

Invite Others: (only in People) This permission allows the person to invite others into the project. The person may only grant permissions to the invitee up to and including their own permission levels.

Commit: (only in Source) This permission allows the person full access to the project’s repository.

With regard to time tracking features, please note that any person who is to have access to time tracking must have both “manage” permissions on tickets and at least “read” permissions on people.

I hope that helps!