Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Resolved Error "Prefix "PRJ" has already been taken" when attempting to edit existing project
#1
I successfully created a new project using a new 1.5.0 install, then attempted editing the project to add an effective start date which resulted in this error.

   

What is the purpose of the Prefix field? Is doesn't seem it should be editable in the new project creation form (as it appears to be now), or checked for uniqueness when a project is updated.
Dale Scott
Transparency with Trust
http://www.dalescott.net
Reply
#2
Hi Dale,
I can confirm that this a bug and it will be fixed on the next MyT release.

The prefix field is used as "prefix" for tasks identifier related to a project, for example if you have a project with prefix PRJ, all the tasks for this project will have the identifier like: PRJ00001, PRJ00002 etc

I've fixed the behavior for this field, it should be unique e will be pre-populated on project creation
Reply
#3
Hi Paolo, thanks for investigating. Is there a workaround? Does this mean that after creating a project, the project cannot be edited (until after upgrading to the next MyT release)? When do you expect the "next MyT release"? Please don't take offence, I don't mean to pressure you. I'm a newb in the community and don't know how things work yet. Someone once said to use three's for estimating time. 3 days? 3 weeks? 3 months?

I was hoping the project might have a public repo or mirror repo. Fwiw, I like git on GitHub and Subversion on Sourceforge (or for free mailing lists). Since the behavior is now fixed in the code, it would be really great if I could pull your patch/commit from a public repo, or perhaps simply follow head/trunk/master and continuously live at the edge. It seems too slow waiting for snapshot .zip packages, but then I'm a newb here and don't know what to expect.

Dale
Dale Scott
Transparency with Trust
http://www.dalescott.net
Reply
#4
Hi Dale,
I think new package will be out during this week-end ( 20th or 21th ), i can share a workaroud but it' requires also the execution of update script ( some record needs to be updated on database ).

About a public repo's we are thinking to move to github, to accept patch e pull requests from community.

Paolo
Reply
#5
(08-19-2016, 09:24 AM)Paolo Wrote: Hi Dale,
I think new package will be out during this week-end ( 20th or 21th ), i can share a workaroud but it' requires also the execution of update script ( some record needs to be updated on database ).

About a public repo's we are thinking to move to github, to accept patch e pull requests from community.

Paolo

I'm waiting for resolution too :-)
Reply
#6
Thanks Paolo. I appreciate your offer of a patch script, but I can wait for the next release if it's only going to be a couple days.

I'm glad to hear you are considering moving to a public repo! Sourceforge supports git, so if you like Sourceforge you don't necessarily have to move the project to Github. My experience is that Github has a much better web interface than Sourceforge, and it's easy to use the web interface to make quick edits directly in a repo on Github (instead of pull/edit/commit/push-or-pull-request), although best practice is to always use a pull-request for better traceability. My only project experience on Sourceforge has been using Subversion, which is perfectly adequate, but I prefer git for how branches are is managed.

Regards,
Dale
Dale Scott
Transparency with Trust
http://www.dalescott.net
Reply
#7
Fyi. I installed the v1.5.1 release but still encountered this error when attempting to edit the description of an existing project.
Dale Scott
Transparency with Trust
http://www.dalescott.net
Reply
#8
Hi Dale,
Can you please check how many project you have on database ( myt_project.prefix ) with prefix = 'PRJ' ?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)