Mantis Bug Tracker - Forums

I believe this is the plugin?
https://github.com/mantisbt-plugins/EasyEnter
That looks useful.

I suggest you contact the author. His address is in EasyEnter.php.
Please ask him to post a solution to this forum!
Thanks.

I use this sequence in KeePass for some Mantis sites: {DELAY=60}{HOME}+{END}{UserName}{ENTER}{DELAY 1000}{HOME}+{END}{Password}{ENTER} This sequence takes much more time but it is much more detailed and never fails with any Mantis site. {DELAY=80}{HOME}+{END}{DELAY 500}{UserName}{DELAY 1000}{ENTER}{...

To be clear, are you trying to move a ticket from Resolved to Deployed?
Based on the workflow settings, no status other than Resolved allows moving forward to Deployed ... which makes sense.

Yes ... if I understand you correctly. From what I understand about what you're doing, you need the events for after user data has been entered, and before it has been posted to the database. See details under: https://www.mantisbt.org/docs/master/en-US/Developers_Guide/html/dev.eventref.bug.action....

I think that's exactly what I've been describing. I will fork it and start looking.
Thanks @cas!!!!!!!!!!!!!!!!!

EVENT_UPDATE_BUG (Execute) : "This event allows plugins to perform post-processing of the bug data structure after being updated."
-- https://www.mantisbt.org/docs/master/en ... gle-plain/

FWIW, I just looked through it closely and it looks good to me. I see you don't have an In Progress status, so tasks go directly from Assigned to Resolved and you don't care exactly when someone is actually working on it - if it's assigned then it's assumed to be in progress. Other than this questio...

Yes, old and ongoing very painful issue.

Questions about plugins might get more views or responses in the Plugins forums.

Yes, Queries would be good to simply report data. But we would lose the formatting and functionality provided by the View page. For example, clicking on fields, and especially mass updates of selected records. There still needs to be a link between the fields selected for a query and the fields whic...

I'd like to understand how others use Change Logs between "published" updates. Example: v1 and v2 are major releases. v1.1 and v1.2 are minor updates v1.1.1 and v1.1.2 are patches which are released as required but they will appear in 1.2 when it is released. Someone enters at ticket against v1.1. I...

Additional note : We know that we can do this because Mantis already supports per-project views. What I'm suggesting here is that views simply get names which can then be assigned as a default to any project, and then the names can be made available in a dropdown in the view page. I think I will be ...

That's where we are now, with one view for everyone with a single configuration. Change the configuration and it's still the same view for everyone. To be clear, there is the view on the page, the CSV view, the Print view, etc. Yes, each one of those has a configuration. But there is only one page v...

Ugh, I've had email_api.php sitting on my desktop for months and I need to make changes. It's just staring at me. "Go ahead, I dare you to start messing with me." I haven't allocated the time to wrestle with the beast. I love that Mantis is so versatile in some ways, but it's so hard-coded in others...

Thanks @cas. But, well, that's a 100% DIY solution with zero % built-in support. I was kinda hoping for slightly better. :wink: I know we have examples for adding buttons to the side, like in the wiki plugin. But creating a new view won't be as easy as cloning view_all_bug_page.php. That page relies...