iridakos / release_logs Goto Github PK

Release log entries, "Note" include unessential heading symbol h4.
Suggest remove it, please.

Is redmine 2.3 support possible ?

In order to use release_logs on Rails 4, it's required to upgrade protected_attributes gem to the latest one at least to 1.1.3, however there is no version dependency specified inside of extension.

So, it works with "protected_attributes" 1.1.3, doesn't work with 1.1.0 (and unsure about interim versions)

A nice small feature would be to ask for confirmation before publishing events.

"Title cannot be blank" error message appears on creating the new Release Log even though Title not empty and properly specified.

Environment:
Redmine version 3.0.3.stable
Ruby version 2.0.0-p645 (2015-04-13) [x64-mingw32]
Rails version 4.2.1
Environment development
Database adapter Mysql2

release_logs 1.0.0

Hi,

I try to get it running on the current version 3.4.x.
But I ran into issues while running migration process (no tables created, etc).

Is there anything to change to support 3.4.x?

If user opens Release Logs through global menu item, he can see all the releases across all the projects even though user has no access to that particular projects. It violates the privacy of projects.

Just like below picture, in the Permissions i already set Project Admin. have permission to modify release log configurations & release log queues.

But in the Project page i can't find release log page.
Please advice where to manage release log configurations & release log queues.

Can not use "Rollback release" & "Cancel release".

Environment:
Redmine version 3.0.5.stable
Ruby version 1.9.3-p551 (2014-11-13) [x86_64-linux]
Rails version 4.2.3
Environment production
Database adapter Mysql2

It'll be useful to have option/button to automatically add closed issues.

Caused by validation & db index on unique (issue_id & release_log_id) in the release log entry model.

Will be nice if we can choose version and auto populate issues and update title with version number.

Plugin is very nice, but with some more automation can be very very useful.

Can you add .travis.yml to test agains many redmine versions (2.6.x 3.0.x)? example

I'm not sure if this makes sense in the plugin's context but I would like to be able to have multiple Release configurations for a single project which is not currently possible (https://github.com/iridakos/release_logs/blob/master/app/controllers/release_log_configurations_controller.rb#L48). With that, one would be a able to send release notifications to different recipients about different issues within that project. Maybe there's another way to achieve that goal?

there is mass-assign problem
eq: WARNING: Can't mass-assign protected attributes for ReleaseLogQueue: name, title_template, email_notification_recipients, group_by_issue_type

I think it's related to #2

Hello,

Just got such error on release log "save & publish" procedure when date and time are specified on Release plan section

NoMethodError (undefined method `in_time_zone' for Fri, 10 Jun 2016:Date):
  plugins/release_logs/app/controllers/release_logs_controller.rb:105:in `save_release_log'
  plugins/release_logs/app/controllers/release_logs_controller.rb:32:in `create'
  actionpack (3.2.22.2) lib/action_controller/metal/implicit_render.rb:4:in `send_action'
  actionpack (3.2.22.2) lib/abstract_controller/base.rb:167:in `process_action'
  actionpack (3.2.22.2) lib/action_controller/metal/rendering.rb:10:in `process_action'

Environment
Redmine: 2.6.10
Ruby: 2.2.3-p173
Rails: 3.2.22.2
Release logs plugin: master

What could be or should be done to avoid this problem?
Thanks in advance

It's not convenient to scroll up the page to find the link to add new entry if you've already added some.

One solution would be to add a signature with a timestamp in release emails.

You can find more information in the following SO question: http://stackoverflow.com/questions/11078264/how-to-get-rid-of-show-trimmed-content-in-gmail-html-emails

Hi,

it would be nice if we could send custom free text notification for users.
We would like to send a notification before we actually deploy so that the users could exit the application like a warning.
Another example is that one issue will be deployed to multiple application. With this custom notification we could signal which one has been deployed.

The plugin is great and help me a lot but I have to do some manual tasks which could be optimized. I try to explain it. If I create a new release log entry it will be helpful if some more information from the ticket will be added to the note field. For example if I could configure somewhere which fields have to be added automatically to the note field I could choose the description field and for example a custom field named solution then I have directly a perfect release notes without typing the solution weeks after the fix.

At this moment, all emails are sent from "Redmine". You need to look inside the email's body to see who published the notification.
It would be nice if the "From" of the notification email was filled with the publisher's email, if available.

Hi,

it would be nice to have hipchat integration. This way we could have a notification for all hipchat users that prefer chat over email.

1. if "Log queue" leave it blank.
   
2. When manually assign a title to release
   
3. Will show the error message "Title cannot be blank", and the title text will be cleared.
   

Environment:

Hi,

it would be nice to see the same description of the release in the final "released" notification.
This way the email recipient can see from the email directly more information and don't need to open redmine. The same is true for the cancellation.

1. Not all users that can manage a release log should be able to delete published logs.
2. The new permission should also allow edition of a published release log.

urrrr, it seems not support clipboard image paste, any solutions?

... it, of course, can be alleviated be re-uploading the attachments to the cloned release log, but it would be nice to have

On the page where you configure a release log:

Administration -> Release log configurations -> Create New

The select that lists all of the site projects is not ordered. For sites with many projects, this makes it difficult to find the project you are looking for. I would suggest ordering the list alphabetically.

It seems that the numbering of the weeks is not in sync with the convention used from various calendars across the world (for example http://www.epochconverter.com/date-and-time/weeknumbers-by-year.php?year=2016).

We created a new release notification for Monday, 01/04/2016 10:00 AM and the title of the email was S16E02 instead of S16E01 that it should be.

Here is the log:

Migrating release_logs (Release Logs plugin)...
== 7 RemoveUniqueuIndexFromReleaseLogEntries: reverting =======================
rake aborted!
An error has occurred, all later migrations canceled:



remove_index is only reversible if given a :column option.

/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration/command_recorder.rb:157:in `invert_remove_index'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration/command_recorder.rb:66:in `inverse_of'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration/command_recorder.rb:50:in `record'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration/command_recorder.rb:83:in `remove_index'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:662:in `block in method_missing'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:632:in `block in say_with_time'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:632:in `say_with_time'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:652:in `method_missing'
/usr/share/redmine-3.0.1/plugins/release_logs/db/migrate/007_remove_uniqueu_index_from_release_log_entries.rb:3:in `change'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:604:in `block in exec_migration'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:493:in `block (2 levels) in revert'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration/command_recorder.rb:38:in `revert'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:493:in `block in revert'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:640:in `suppress_messages'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:492:in `revert'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:604:in `exec_migration'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:590:in `block (2 levels) in migrate'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:589:in `block in migrate'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/connection_adapters/abstract/connection_pool.rb:292:in `with_connection'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:588:in `migrate'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:765:in `migrate'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:995:in `block in execute_migration_in_transaction'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:1043:in `ddl_transaction'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:994:in `execute_migration_in_transaction'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:956:in `block in migrate'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:952:in `each'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:952:in `migrate'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:827:in `down'
/usr/local/rvm/gems/ruby-2.1.5/gems/activerecord-4.2.0/lib/active_record/migration.rb:802:in `migrate'
/usr/share/redmine-3.0.1/lib/redmine/plugin.rb:474:in `migrate_plugin'
/usr/share/redmine-3.0.1/lib/redmine/plugin.rb:446:in `migrate'
/usr/share/redmine-3.0.1/lib/redmine/plugin.rb:457:in `migrate'
/usr/share/redmine-3.0.1/lib/tasks/redmine.rake:127:in `block (3 levels) in <top (required)>'
/usr/local/rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `eval'
/usr/local/rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `<main>'
Tasks: TOP => redmine:plugins:migrate
(See full trace by running task with --trace)