Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create issue does nothing #30

Closed
manwe opened this issue May 10, 2019 · 26 comments
Closed

Create issue does nothing #30

manwe opened this issue May 10, 2019 · 26 comments
Labels
invalid This doesn't seem right

Comments

@manwe
Copy link

manwe commented May 10, 2019

When sending text to the bot, I have two options: Create issue and add note. When choosing the first one nothing happens, no other options offered. Adding a note asks for more options.

Debug log:

{"update_id":836342763, "callback_query":{"id":"586585762160892758","from":{"id":136575140,"is_bot":false,"first_name":"Jon","last_name":"Bonilla","username":"jbmanwe","language_code":"es"},"message":{"message_id":17,"from":{"id":863583925,"is_bot":true,"first_name":"ubsoporte","username":"ubsoporte_bot"},"chat":{"id":136575140,"first_name":"Jon","last_name":"Bonilla","username":"jbmanwe","type":"private"},"date":1557483165,"reply_to_message":{"message_id":16,"from":{"id":136575140,"is_bot":false,"first_name":"Jon","last_name":"Bonilla","username":"jbmanwe","language_code":"es"},"chat":{"id":136575140,"first_name":"Jon","last_name":"Bonilla","username":"jbmanwe","type":"private"},"date":1557483165,"text":"Echen"},"text":"Select an action from:"},"chat_instance":"-3778251224232573802","data":"{"rb":{"gp":{"id":0,"p":1,"fp":1}}}"}}
[2019-05-10 12:13:10] bot_log.DEBUG: Verbose HTTP Request output:

  • Expire in 0 ms for 6 (transfer 0x55b0b3003d30)
  • Expire in 30000 ms for 8 (transfer 0x55b0b3003d30)
  • Expire in 150000 ms for 2 (transfer 0x55b0b3003d30)
  • Expire in 1 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 1 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 1 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 1 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 1 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 1 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 1 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 1 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 1 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 1 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 1 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Expire in 0 ms for 1 (transfer 0x55b0b3003d30)
  • Trying 149.154.167.220...
  • TCP_NODELAY set
  • Expire in 15000 ms for 3 (transfer 0x55b0b3003d30)
  • Expire in 200 ms for 4 (transfer 0x55b0b3003d30)
  • Connected to api.telegram.org (149.154.167.220) port 443 (#0)
  • ALPN, offering http/1.1
  • successfully set certificate verify locations:
  • CAfile: none
    CApath: /etc/ssl/certs
  • NPN, negotiated HTTP1.1
  • SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
  • ALPN, server did not agree to a protocol
  • Server certificate:
  • subject: OU=Domain Control Validated; CN=api.telegram.org
  • start date: May 4 14:42:31 2018 GMT
  • expire date: May 23 16:17:38 2020 GMT
  • subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org"
  • issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
  • SSL certificate verify ok.

POST /bot863583925:AAF-2vQFFFFFFFFFFFFFFMhyubVr0/answerCallbackQuery HTTP/1.1
Host: api.telegram.org
User-Agent: GuzzleHttp/6.3.3 curl/7.64.0 PHP/7.3.4-2
Content-Type: application/x-www-form-urlencoded
Content-Length: 36

  • upload completely sent off: 36 out of 36 bytes
    < HTTP/1.1 200 OK
    < Server: nginx/1.12.2
    < Date: Fri, 10 May 2019 10:13:10 GMT
    < Content-Type: application/json
    < Content-Length: 25
    < Connection: keep-alive
    < Access-Control-Allow-Origin: *
    < Access-Control-Allow-Methods: GET, POST, OPTIONS
    < Access-Control-Expose-Headers: Content-Length,Content-Type,Date,Server,Connection
    < Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
    <
  • Connection #0 to host api.telegram.org left intact

[] []
@brlumen
Copy link
Member

brlumen commented May 10, 2019 via email

@brlumen
Copy link
Member

brlumen commented May 10, 2019 via email

@manwe
Copy link
Author

manwe commented May 10, 2019

My user is administrator. I'm testing it. I do have issue creation rights.
We're using php 7.3.4 (debian buster) and mantisbt 2.20.0
Plugin version is 1.5.0 (downloaded today)

@brlumen
Copy link
Member

brlumen commented May 12, 2019

Are there any error messages on the page "plugin.php? page = TelegramBot / monitor_page" ?

@manwe
Copy link
Author

manwe commented May 12, 2019

Are there any error messages on the page "plugin.php? page = TelegramBot / monitor_page" ?

None

@brlumen
Copy link
Member

brlumen commented May 12, 2019

Please send me your mantisbt configuration file. Clear confidential information before shipping.

@manwe
Copy link
Author

manwe commented May 13, 2019

I'm receiving notifications when a note has been added or a ticket assigned. Looks good but can't create issues from telegram.

@brlumen
Copy link
Member

brlumen commented May 13, 2019

Can you add notes through the bot?

@manwe
Copy link
Author

manwe commented May 13, 2019 via email

@manwe
Copy link
Author

manwe commented May 13, 2019

Can you add notes through the bot?

Yes, I can

@brlumen
Copy link
Member

brlumen commented May 13, 2019

El Sun, 12 May 2019 02:23:29 -0700 Grigoriy notifications@github.com escribió:
Please send me your mantisbt configuration file. Clear confidential information before shipping.
Attached. thank you
…
-- https://pekepbx.com https://www.issabel.com/multitenant

Where did you attach the file?

@manwe
Copy link
Author

manwe commented May 13, 2019

ohm. I answered via email and attached the file. I thought that would work.
Here's a link to the file:
config file

@brlumen
Copy link
Member

brlumen commented May 13, 2019

I managed to reproduce the error.
Looking for reasons for what could be the problem.

@brlumen
Copy link
Member

brlumen commented May 13, 2019

Most likely, in your user settings, the default project is no longer an existing project.

Please set the correct project as default.
Note that the plugin repeats the logic of mantisbt behavior and if the default project is set as a project in the user settings, not "All projects", the TelegramBot will not offer to select a project when creating an issue, but create an issue with the default project.

@brlumen
Copy link
Member

brlumen commented May 13, 2019

If you have only one project and on the user configuration page it seems to be selected correctly, anyway, try setting it again.
Then you need to send any text to the bot so that it can complete the process of creating an issue with a bad-draft project.
Upon completion, the bot must report that the project does not exist and then everything should work fine.

@manwe
Copy link
Author

manwe commented May 13, 2019

If you have only one project and on the user configuration page it seems to be selected correctly, anyway, try setting it again.
Then you need to send any text to the bot so that it can complete the process of creating an issue with a bad-draft project.
Upon completion, the bot must report that the project does not exist and then everything should work fine.

My default project is "All projects"

Changed the default to one specific project and it worked.
Changed ot another spcecific proyect which required a custom field to be filed to create the issue and failed.

Should it work when "all projects" (Todos los projectos) is my default?

@brlumen
Copy link
Member

brlumen commented May 13, 2019

Of course it should work. Moreover, only in this configuration, the bot will choose a project.

Unfortunately, projects with custom fields are currently not supported.
But at this stage such a project should not affect the work of the bot.

Tell us more about your projects structure. How many of them? The depth of the hierarchy? What type of custom field are you using?

@josemaX
Copy link

josemaX commented May 13, 2019

Hello, I have this problem, i think is the same Issue 22 i opened some time ago #22

I receive notifications about new issues by Mail (my user: admin) but no by TelegramBot. Then when commented then receive Telegram notifications.

@josemaX
Copy link

josemaX commented May 13, 2019

Well i just solved it for me with 1.5.0 this way

Manage->Manage Plugins->TelegramBot 1.5.0->[Configure Notifications]

In section "Any user with access level"->"Administrator" place a mark for "Status changes to 'new'"

I missed that, but is very reasonable the need to place that, so you receive notifications if you are admin and new issues are submitted.

Impersonated an user and sent an issue as him, the notification arrived immediately.

Hope this helps some one

Thanks by the plugin!!!

@brlumen
Copy link
Member

brlumen commented May 14, 2019

@josemaX Thank you for your feedback, but unfortunately this is not related to this issue.

@brlumen
Copy link
Member

brlumen commented May 14, 2019

@manwe I compared your configuration file with the default configuration file for your version of mantis. It seems that you are using the configuration file version 1.2 and partly from 2.20. On my installation, I can not run a mantisbt, he swears at the base.

Could you check your installation with the minimum possible settings from the default settings?

@brlumen
Copy link
Member

brlumen commented May 14, 2019 •
edited
Loading

I tried many options, but could not reproduce your mistake.
For further diagnostics, I need the mantisbt log and web server logs.
The matntisbt log can be activated via the configuration parameter $g_log_level = LOG_ALL

@manwe
Copy link
Author

manwe commented May 14, 2019

@brlumen At this point:

  • Notifications work
  • We can reply to notifications and add issues.

This is more than enough for us and we're very happy with the plugin. Thank you very much for coding and for your support.

Regarding your other questions: We use it for customer support. We have around 300 projects and a 3 level deepth tree. Around 800 users can report but I guess few of them will use telegram. It will be mostly for our support team.

Creating issues when you have a default project with no custom fields works. I don't think pleaople will use it for creation rather than notifications and adding quick notes. Our custom field for issue creation is usually a contact phone number (numeric field lenght 9).

We don't need anything else and we're very gratefull to you. I can do some more debugging if that helps your development.

cheers,

Jon

@brlumen
Copy link
Member

brlumen commented May 14, 2019

I'm glad I could help you.
If you ever find out what the problem was, tell me please.

Good luck!

@brlumen brlumen closed this as completed May 14, 2019
@brlumen
Copy link
Member

brlumen commented May 14, 2019

I have a new idea. Perhaps a problem due to the number of projects. I did not limit the number of zero nesting projects, while telegrams have limitations on the number of buttons.
I will re-issue and try to check.

@brlumen brlumen reopened this May 14, 2019
@brlumen
Copy link
Member

brlumen commented May 14, 2019

Unfortunately the version was not confirmed.
I close this issue.

@brlumen brlumen closed this as completed May 14, 2019
@brlumen brlumen added the invalid This doesn't seem right label May 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
invalid This doesn't seem right
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@josemaX @manwe @brlumen