Taiga-front: Feature request: Remove username from project slug

[tanc]

As discussed with @superalex just now, this is a feature request to remove the username portion of the url slug for a project. It looks quite weird to customers when their project url is prepended with the username of the person opening the project. If some kind of identifier is needed to make the url unique maybe a project shortname or set of characters could be requested when creating a project?

[kabaka]

Agreed.

It only took about an hour after setting this up for someone to ask me why my name was on every URL.

[kabaka]

The more I think about this, the more I realize that some kind of prefix is probably necessary. I feel like the most ideal fix would require support for organizations, so that the organization name could be used as the prefix. I did't see an open request for such a feature, so I have added it as #653.

For self-hosted projects, which I believe this ticket really refers to, this should probably be some kind of configuration option system-wide. Otherwise, the Django admin interface does a good job of letting us edit slugs.

[LongLiveCHIEF]

+1

[n11c]

+1

[vibhor-trantor]

+1

[Mr-Snailman]

+1

[fabue]

+1

[kaazoo]

+1

[vibhor-trantor]

+1

[cyberdie]

+1

[herbsmn]

+1

[stevenroose]

There should be a slug-template field in the admin panel that defaults to "%u-%n", but that can be changed to just "%n".

[herbsmn]

@stevenroose can this be done manually right now?

[stevenroose]

@herbsmn You can change the slugs individually... I did that for the
projects I created. It's in the admin panel at
https://your.taiga.site/admin/ (mind the ending slash).

On Thu, Sep 15, 2016 at 10:43 PM, herbsmn [email protected] wrote:

@stevenroose https://github.com/stevenroose can this be done manually
right now?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/taigaio/taiga-front/issues/652#issuecomment-247449842,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0F3LLmWelJHTiQFVcpY5pEC5BtgsGDks5qqa33gaJpZM4GDAuS
.

[herbsmn]

this is super helpful @stevenroose! I didn't even know about the admin panel!

[herbsmn]

looks like you have to do this slug name change before doing stuff in projects or else it will break some links.

[stevenroose]

Yeah, if you have any links to the projects in which the slug appears, you
should watch out changing it. Btw, make sure you change the admin password
for the admin dashboard. I guess a lot of users don't know about the
dashboard and still have the admin/123123 active, which is really dangerous.

On Thu, Sep 15, 2016 at 11:41 PM, herbsmn [email protected] wrote:

looks like you have to do this slug name change before doing stuff in
projects or else it will break some links.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/taigaio/taiga-front/issues/652#issuecomment-247463631,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0F3DLCMF1Xlmf_-7Twgl1mAcdsyvHCks5qqbuLgaJpZM4GDAuS
.

[herbsmn]

@stevenroose yeah, that's a pretty big security problem having people not know about this. I luckily changed my admin password right away even though I didn't know about the admin panel at the time. I assumed something like that existed though.

[rlataguerra]

after you changed the slug you have the regenerate the projects timeline otherwise links on project timeline will be broken :

python manage.py rebuild_timeline --purge

[bameda]

@stickyhands there is a console command to change the project slug

usage: manage.py change_project_slug current_slug new_slug

Change the project slug from a new one

positional arguments:
  current_slug          The current project slug
  new_slug              The new project slug

[neknalb]

+1

[laszlo-apro]

Hi guys,

I'm wondering if there is any update on this fairly old thread? It's a serious issue, and I presume a lot of us want it to be solved as soon as possible. It looks really unprofessional having the project creator's username in the URL.

Hope you will come up with a solution in the near future.

Regards,
Laszlo

[rastapopougros]

+1 and more, it's so damn weird! :smiley:

The goal of a project manager like taiga is to work… with your team. Like… always. So it doesn't make sense to have the name of one person in the URL. :smile:.

The new project is almost always for everyone, and maybe few months later, the person who created the project will no more work on it…

• Hey come work with us for SuperClient in the project : ourtaiga.org/project/charlie-superclient/timeline
• Ok thanks. Eh who is Charlie ?
• Hum, don't know… Maybe I remember a guy working here in 2003…"
  :rofl:

[rastapopougros]

Also, to be a bit more constructive, the ergonomic solution is very simple : provide an explicit field to define the project slug in the creation form.

When the user enters the project human name, the slug could be pre-generated (with a prefix/suffix or not). But it can be modified.

And when the user submits the form, there is a validation for this field, checking not already used, and error message if that's the case.

[dhruv-bansal]

hey everybody, any update on this thread. Can I remove the username from my git repo project URL?

[tanc]

There are currently two methods I know of, if you have a self-hosted instance:

Method 1:
Visit the admin panel at https://your.taiga.site/admin/ (mind the ending slash)
Click on Projects link under Projects section
Click on your newly created project
Edit the Slug field and save the project

Method 2:
Use the console command:

usage: manage.py change_project_slug current_slug new_slug

Change the project slug from a new one

positional arguments:
  current_slug          The current project slug
  new_slug              The new project slug

It has been five years since my original request but as far as I can tell only @bameda from Taiga has replied with a solution (useful only if you have server access). It would be good to hear from the devs about whether this is something in scope for a future release and if not why they don't want to implement it.

[rastapopougros]

We use the first method since our start with Taiga, but it's obviously technical and anti-ergonomic :)
That's why I suggested to have a pre-generated slug field directly inside the normal new project form, with a unicity test on it (and that's the way Drupal or other systems manage the slugs : never hidden).

To go in this direction, an other argument : some could say "slug is a technical thing, we don't want to see that in an interface". And that's totally wrong. Slug is used in all URL and sub-URL of the project. And URL is the very first thing all end-users see of a place on internet. It's one of the first thing you learn when you study ergonomy and UX : there is not only the final interface, but how users find the place before. It's this URL anyone copy and paste in messages to others "hey my friend, watch how we work in our super projet here : …".

So because URL is important, slug is important, and then it must not be hidden but it must be chosen explicitly in the create form.

[NatachaMenjibar]

We have been doing some housekeeping work prior to Taiga6 upcoming release and we are reviewing old issues that we didn't correctly attend back then. Taiga6 brings a significant UX/UI rework, and after the launch, we’ll come back to this issue as it’s part of our roadmap. This time we will make sure to review it properly.

Thank you very much on behalf of the Taiga Team!