I'd like to add some Custom fields to Notes which Issues belong to.
pic1
I've read the guide below:
http://www.redmine.org/projects/redmine/wiki/RedmineCustomFields
On that page, I can see Fields for Issues, Fields for Spent time entries and Fields for Activities. But It seems that there is no information I'm looking for.
Are there any settings or plugins?
I'm using 2.6.6.stable for now. But I'll update Redmine to latest version if needed.
Thanks in advance.
unfortunatelly, there is no custom field for issue updates (notes), only for tickets itself.
Anyway, I strongly recommand to upgrade to the latest production version.
Regards
Maxim
Related
I am looking for a package or hints on how to track each field and the ability to accept or reject editing
i using Django 1.11 and python3
Package like:
django_monitor not working
django_approve not working
It sounds like django-moderation should fit you need. I haven't used it personally, but the docs mention that it's possible to have changes displayed only after a moderator accepts them, and there is also an option (keep_history) to maintain the history of the changes made to a model.
You see the MySQL tables in the Sequel Pro, every field has a Comment:
Whether I can set the field comment in the Model?
class Account(models.Model):
balance = models.CharField(max_length=16)
grade = models.CharField(max_length=1, default=1) # whether there is a property for us to set field comment?
You can't set comment on a field in django (please check this issue)
I understand the idea, but I'm afraid it doesn't have a good
usefulness/noise ratio.
The ORM doesn't aim at providing a Python interface for every feature
of the supported database engines. Its goal is "just" to provide an OO
API.
Since there's neither a clean API proposal, nor a patch, nor a
convincing explanation of the value added by this feature, I'm going
to close this ticket.
PS: you can use django raw sql queries and manually set the comment.
As I've answered in a similar question:
Ticket #13867 is now "superseded" by #18468, which was reopened and is now accepted and waiting for patches. The original rejection, after discussion on the mailing list, changed to
I think we could implement that feature. (Yes I changed my mind from six years ago when I wontfix'd the ticket.)
A partial solution, for PostgreSQL databases, is published at https://github.com/vanadium23/django-db-comments, as a post-migration hook Django app. Should not be hard to adjust it for MySQL databases.
I've recently started tampering with Mezzanine and I am trying to add 2 new fields to the Blog Post admin -- keywords, and meta title.
I did it by editing my admin.py file and adding the following:
from mezzanine.blog.admin import BlogPostAdmin
from mezzanine.generic.models import Keyword, AssignedKeyword
BlogPostAdmin.fieldsets[0][1]["fields"].extend(["keywords"])
BlogPostAdmin.fieldsets[0][1]["fields"].extend(["_meta_title"])
admin.site.register(Keyword)
admin.site.register(AssignedKeyword)
I see the fields in the blog post manager, but when I edit them specific to a blog post, they don't save to that post. However, if I am adding keywords, the keywords get saved to the overall site keywords (generic_keyword table).
Is there any way to make them also update the blog post such that _meta_title and keywords_string gets updated in blog_blogpost? Thanks for any help.
EDIT: After looking into this further, it doesn't seem that I need to do anything to get the "Meta Data" section to be expandable. However, in my copy, it cannot be expanded. Is there any particular reason for this?
The answer above is a bit incomplete, and will be misleading for anyone who comes across the same problem.
My guess is that at some point you copied the admin's base_site.html template into your project, from an older version of Mezzanine. You've then later upgraded to a newer version of Mezzanine, which refers to an upgraded version of chosen - you can see the commit from 3 months ago here where that occurred here: https://github.com/stephenmcd/mezzanine/commit/f4e33282eaac44ef8ebbadb9b0157d910c67973a
If anyone experiences this issue, check your javascript console. In my case, for whatever reason, the Admin section was trying to load mezzanine/chosen/chosen-0.9.12.jquery.js which doesn't exist. I edited blog/templates/admin/base_site.html and updated it to mezzanine/chosen/chosen.jquery.js and the Meta Data section became expandable/collapsible again.
I am currently working to write a web app where people fill out the necessary information, and apply to their mentors.
So, at this point, mentors have a model class that is pretty much like the applicant's, so that they can correct the applicant's info without affecting the applicant's original profile.
I will appreciate any helpful comments. Specifically, I am looking for:
-A similar per-exisiting django app that does more or less so I can browse the source.
-Any special Django feature that allows this that I can not aware of.
-General info on how things like these are done in general.
Thank you.
Ad general info)
You would benefit from doing this in a single model (say ApplicationModel), with fields in pairs - field_name_applicant, field_name_mentor.
Then use a CreateView with its fields property set to only the *_applicant fields for the applicant to fill in the applications initially, and an UpdateView with its fields set to the *_mentor fields for the mentor to correct the applicant fields.
Have ApplicationModel.clean() copy all *_applicant field values to their *_mentor counterpart if the later is not set.
Now you have all your business logic in the model where it belongs; quoting a headline in the introduction of Two Scoops of Django:
Fat Models, Helper Modules, Thin Views, Stupid Templates
I am building a site where users can make changes to their publicaly displayed profile. However I need all changes to be approved by an admin before going live. Until the changes are approved their old profile will be displayed. In the admin there should be a list of profiles awaiting approval. It is preferable, but not required, to keep a history of versions.
I have looked at django-reversion, but don't think that will handle showing an old version while keeping a new one under-approval.
I'm looking for ways to achieve this with django...
Two from-the-hip ideas. How about...
Use reversion and add logic which auto-marks a profile as 'unapproved' on save() if the save is not performed by an administrator, then add a custom accessor to your code that gets the latest approved profile from the reversion archive.
Or, if reversion won't play nicely, have a 'current profile' and 'pending profile' for each user and update the FKs when the profile is approved...
This apps do exactly what you need
http://github.com/dominno/django-moderation
I've had some problems using django-moderation from dominno, which are:
Using a unique model for tracking changes in several others, with a GenericForeignKey reduces the amount of tables needed to monitor things, but it's a pain to manage. And I don't trush GenericForeignKeys for this type of task.
Deserialization of sandboxed values would invariably fail if I changed one field's name in the model. (for example, if I migrated a field change of name after monitoring it in moderation). It should at least be able to recover non bogus field values.
So I made my own app, which tackles the problems mentioned above.
It should give you what you're looking for.
https://github.com/artscoop/django-approval
It has auto approval mechanism, field selection (you can always ignore some fields, and put others to validation) and default values (for example, automatically set an object to hidden when it's created, so that it can be moderated without being visible in the first place)