Re: crashed workflow
"Mauro Durante Jr." <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.mantis.general |
|---|---|
| Message-ID | <[email protected]> |
here is it.. thanks, Mauro. On Wed, Jul 15, 2009 at 4:46 PM, Glenn Henshaw <thraxisp-3kkvZBxzQh2+Mgy9Xt2BoPd9D2ou9A/[email protected]>wrote: > > On 15-Jul-09, at 8:26 AM, [email protected] wrote: > > > I´m resetting it through a button in Mantis Management section... > > > > Yep, I copied it (config_inc.php) from 1.1.1 to 1.1.7. > > > > However I guess it should work, once the workflow was defined and > > kept during the Mantis update. > > Just a note that configs can be set in both the config_inc.php file > (for global implementation or changes to defaults) and the GUI (stored > in the database). The GUI setting DOES override the setting in the > config_inc.php file. If you make changes there, and they are not > taking effect, check the database for an override. > > AFAIK, there weren't any workflow changes between those two releases. > > I would need some more information to diagnose the problem (i.e., > relevant settings from config_inc.php and database). > > ... Glenn > > > > > > > Thanks, > > Mauro. > > > > On Jul 15, 2009 8:57am, KM <info4km-/[email protected]> wrote: > > > > > > > > > Are you resetting the workflow states in your config file or > > something - that's all I can think of. > > > > > > > > > > > > All you did was copy your config files? I may still have my old > > 1.1.1 config files - I can see if there are large differences > > between then and now - > > > > > > > > > > > > Anyone ? > > > > > > KM > > > > > > --- On Mon, 7/13/09, [email protected] [email protected]> > > wrote: > > > > > > > > > > > > From: [email protected] [email protected]> > > > Subject: Re: [mantisbt-help] crashed workflow > > > To: "Help with Mantis" [email protected]> > > > Date: Monday, July 13, 2009, 11:22 AM > > > > > > > > > and it still doesn´t work.. > > > > > > any idea? > > > > > > On Jul 13, 2009 10:38am, [email protected] wrote: > > > > Hi KM, > > > > > > > > thanks for your answer.. > > > > > > > > but the workflow is properly set, every step has its input and > > output. > > > > > > > > I really dunno what´s wrong.. > > > > I´ll try to reset one workflow to check whether it works or > > still gets stuck. > > > > > > > > Thanks, > > > > Mauro > > > > > > > > On Jul 13, 2009 10:02am, KM info4km-/[email protected]> wrote: > > > > > Mauro, > > > > > > > > > > You should be able to go into the 'Manage' functions to fix > > the Workflow Transitions. > > > > > > > > > > > > > > > > > > > > Make sure that you see that 'assigned' issues can go to the > > next desired level - and if not click the boxes accordingly to set > > it up again. You may also modify the access levels (by role) as to > > which level/role can move an issue to a certain > > > level. > > > > > > > > > > > > > > > > > > > > One thing that may be easier is to set it back to the original > > defaults and start over. The button is at the bottom of the screen. > > However be sure that you want to do this ! > > > > > > > > > > > > > > > > > > > > However this doesn't really explain why it happened. I hope > > this helps at all. > > > > > > > > > > KM > > > > > > > > > > > > > > > --- On Mon, 7/13/09, [email protected] > > [email protected]> wrote: > > > > > > > > > > > > > > > > > > > > From: [email protected] [email protected]> > > > > > Subject: [mantisbt-help] crashed workflow > > > > > To: "Help with Mantis" [email protected]> > > > > > Date: Monday, July 13, 2009, 8:23 AM > > > > > > > > > > > > > > > Hi! > > > > > > > > > > I´ve recently updated my old Mantis 1.1.1 to a new 1.1.7, but > > there´s a > > > problem which I cannot go through.. > > > > > > > > > > When a bug is set to "assigned", my workflow leads it to > > "resolved" as next step, and "developer" is the lowest required > > access level to change it. > > > > > > > > > > However, developers cannot set an "assigned" issue to > > "resolved" as they were used to do through "Viewing Issue Simple > > Details" screen, even though it´s possible, but not desired neither > > smart, through "view issues" -> "move" (combo box). > > > > > > > > > > The unique available button on "Viewing Issue Simple Details" > > screen, to developers when an issue is "assigned", is "monitor issue". > > > > > > > > > > I guess something´s wrong with my workflow or user´s > > permissions..but I´m not sure, since it used to work properly on the > > previous (1.1.1) version. > > > > > > > > > > How can I put that "set status to:" button back? > > > > > > > > > > // I´ve copied my "old" config_inc.php file > > > to this > > > > > version. > > > > > > > > > > > > > > > Thanks in advance, > > > > > Mauro > > > > > > > > > > http://www.mantisbt.org/forums/viewtopic.php?f=3&t=7212#p19735 > > > > > > > > > > > -----Inline Attachment Follows----- > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > > > Enter the BlackBerry Developer Challenge > > > > > This is your chance to win up to $100,000 in prizes! For a > > limited time, > > > > > vendors submitting new applications to BlackBerry App > > World(TM) will have > > > > > the opportunity to enter the BlackBerry Developer Challenge. > > See full prize > > > > > details at: http://p.sf.net/sfu/Challenge > > > > > > > > > > -----Inline Attachment Follows----- > > > > > > > > > > > > > > > _______________________________________________ > > > > > mantisbt-help mailing > > > list > > > > > [email protected] > > > > > https://lists.sourceforge.net/lists/listinfo/mantisbt-help > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -----Inline Attachment Follows----- > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > Enter the BlackBerry Developer Challenge > > > This is your chance to win up to $100,000 in prizes! For a limited > > time, > > > vendors submitting new applications to BlackBerry App World(TM) > > will have > > > the opportunity to enter the BlackBerry Developer Challenge. See > > full prize > > > details at: http://p.sf.net/sfu/Challenge > > > > > > -----Inline Attachment Follows----- > > > > > > > > > _______________________________________________ > > > mantisbt-help mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/mantisbt-help > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > Enter the BlackBerry Developer Challenge > > This is your chance to win up to $100,000 in prizes! For a limited > > time, > > vendors submitting new applications to BlackBerry App World(TM) will > > have > > the opportunity to enter the BlackBerry Developer Challenge. See > > full prize > > details at: > http://p.sf.net/sfu/Challenge_______________________________________________ > > mantisbt-help mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/mantisbt-help > > -- > Glenn Henshaw Logical Outcome Ltd. > e: thraxisp-3kkvZBxzQh2+Mgy9Xt2BoPd9D2ou9A/[email protected] w: www.logicaloutcome.ca > Mantis Developer and User since 2002 > > > > > > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > mantisbt-help mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mantisbt-help > ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ mantisbt-help mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mantisbt-help
config_inc.php
(application/octet-stream, 6.3 KB)
<?php
$g_hostname='localhost';
$g_db_type='mysql';
$g_database_name='';
$g_db_username='';
$g_db_password='';
#############################
# Mantis Email Settings
#############################
# --- email variables -------------
$g_administrator_email = '@';
$g_webmaster_email = '@';
# the sender email, part of 'From: ' header in emails
$g_from_email = '@';
# the sender name, part of 'From: ' header in emails
$g_from_name = 'Mantis Bug Tracker';
# the return address for bounced mail
$g_return_path_email = '@';
# allow email notification
# note that if this is disabled, sign-up and password reset messages will
# not be sent.
$g_enable_email_notification = ON;
# The following two config options allow you to control who should get email
# notifications on different actions/statuses. The first option (default_notify_flags)
# sets the default values for different user categories. The user categories
# are:
#
# 'reporter': the reporter of the bug
# 'handler': the handler of the bug
# 'monitor': users who are monitoring a bug
# 'bugnotes': users who have added a bugnote to the bug
# 'threshold_max': all users with access <= max
# 'threshold_min': ..and with access >= min
#
# The second config option (notify_flags) sets overrides for specific actions/statuses.
# If a user category is not listed for an action, the default from the config
# option above is used. The possible actions are:
#
# 'new': a new bug has been added
# 'owner': a bug has been assigned to a new owner
# 'reopened': a bug has been reopened
# 'deleted': a bug has been deleted
# 'updated': a bug has been updated
# 'bugnote': a bugnote has been added to a bug
# 'sponsor': sponsorship has changed on this bug
# 'relation': a relationship has changed on this bug
# '<status>': eg: 'resolved', 'closed', 'feedback', 'acknowledged', ...etc.
# this list corresponds to $g_status_enum_string
#
# If you wanted to have all developers get notified of new bugs you might add
# the following lines to your config file:
#
# $g_notify_flags['new']['threshold_min'] = DEVELOPER;
# $g_notify_flags['new']['threshold_max'] = DEVELOPER;
#
# You might want to do something similar so all managers are notified when a
# bug is closed. If you didn't want reporters to be notified when a bug is
# closed (only when it is resolved) you would use:
#
# $g_notify_flags['closed']['reporter'] = OFF;
$g_default_notify_flags = array('reporter' => ON,
'handler' => ON,
'monitor' => ON,
'bugnotes' => ON,
'threshold_min' => REPORTER,
'threshold_max' => ADMINISTRATOR);
# We don't need to send these notifications on new bugs
# (see above for info on this config option)
#@@@ (though I'm not sure they need to be turned off anymore
# - there just won't be anyone in those categories)
# I guess it serves as an example and a placeholder for this
# config option
$g_notify_flags['new'] = array('bugnotes' => OFF,
'monitor' => OFF,
'reporter' => OFF,
'developer' => OFF,
'viewer' => OFF
);
$g_notify_flags['closed'] = array('manager' => ON,
'bugnotes' => OFF,
'monitor' => OFF,
'reporter' => OFF,
'developer' => OFF,
'viewer' => OFF
);
# Whether user's should receive emails for their own actions
$g_email_receive_own = OFF;
# set to OFF to disable email check
$g_validate_email = ( substr( php_uname(), 0, 7 ) == 'Windows' ) ? OFF : ON;
$g_check_mx_record = OFF; # Not supported under Windows.
# if ON, allow the user to omit an email field
# note if you allow users to create their own accounts, they
# must specify an email at that point, no matter what the value
# of this option is. Otherwise they wouldn't get their passwords.
$g_allow_blank_email = OFF;
# Only allow and send email to addresses in the given domain
# For example:
# $g_limit_email_domain = 'users.sourceforge.net';
$g_limit_email_domain = OFF;
# This specifies the access level that is needed to get the mailto: links.
$g_show_user_email_threshold = REPORTER;
# If use_x_priority is set to ON, what should the value be?
# Urgent = 1, Not Urgent = 5, Disable = 0
# Note: some MTAs interpret X-Priority = 0 to mean 'Very Urgent'
$g_mail_priority = 1;
# select the method to mail by:
# 0 - mail()
# 1 - sendmail
# 2 - SMTP
$g_phpMailer_method = 1;
# This option allows you to use a remote SMTP host. Must use the phpMailer script
# One or more hosts, separated by a semicolon, can be listed.
# You can also specify a different port for each host by using this
# format: [hostname:port] (e.g. "smtp1.example.com:25;smtp2.example.com").
# Hosts will be tried in order.
$g_smtp_host = '';
# These options allow you to use SMTP Authentication when you use a remote
# SMTP host with phpMailer. If smtp_username is not '' then the username
# and password will be used when logging in to the SMTP server.
$g_smtp_username = '';
$g_smtp_password = '';
# It is recommended to use a cronjob or a scheduler task to send emails.
# The cronjob should typically run every 5 minutes. If no cronjob is used,
# then user will have to wait for emails to be sent after performing an action
# which triggers notifications. This slows user performance.
$g_email_send_using_cronjob = OFF;
# Specify whether e-mails should be sent with the category set or not. This is tested
# with Microsoft Outlook. More testing for this feature + other formats will be added
# in the future.
# OFF, EMAIL_CATEGORY_PROJECT_CATEGORY (format: [Project] Category)
$g_email_set_category = OFF;
# --- email separator and padding ------------
$g_email_separator1 = str_pad('', 70, '=');
$g_email_separator2 = str_pad('', 70, '-');
$g_email_padding_length = 28;
# TestLink Config
$g_allow_anonymous_login=OFF;
#$g_anonymous_account = 'testlink';
# Account Creation
# --- signup default ---------------
# look in constant_inc.php for values
$g_default_new_account_access_level = REPORTER;
$g_allow_signup = OFF;
?>