Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / DataFire/Integrations issues and pull requests
#40 - Please merge pull request for MailboxValidator integration
Issue -
State: open - Opened by MailboxValidator almost 5 years ago
#40 - Please merge pull request for MailboxValidator integration
Issue -
State: open - Opened by MailboxValidator almost 5 years ago
#39 - Integration for Vtiger (opensource) and GravityForms
Issue -
State: open - Opened by Patriciawa almost 5 years ago
- 1 comment
#39 - Integration for Vtiger (opensource) and GravityForms
Issue -
State: open - Opened by Patriciawa almost 5 years ago
- 1 comment
#39 - Integration for Vtiger (opensource) and GravityForms
Issue -
State: open - Opened by Patriciawa almost 5 years ago
- 1 comment
#39 - Integration for Vtiger (opensource) and GravityForms
Issue -
State: open - Opened by Patriciawa almost 5 years ago
- 1 comment
#39 - Integration for Vtiger (opensource) and GravityForms
Issue -
State: open - Opened by Patriciawa almost 5 years ago
- 1 comment
#39 - Integration for Vtiger (opensource) and GravityForms
Issue -
State: open - Opened by Patriciawa almost 5 years ago
- 1 comment
#38 - MailboxValidator integration
Pull Request -
State: open - Opened by MailboxValidator almost 5 years ago
#38 - MailboxValidator integration
Pull Request -
State: open - Opened by MailboxValidator almost 5 years ago
#38 - MailboxValidator integration
Pull Request -
State: open - Opened by MailboxValidator almost 5 years ago
#38 - MailboxValidator integration
Pull Request -
State: open - Opened by MailboxValidator almost 5 years ago
#38 - MailboxValidator integration
Pull Request -
State: open - Opened by MailboxValidator almost 5 years ago
#38 - MailboxValidator integration
Pull Request -
State: open - Opened by MailboxValidator almost 5 years ago
#37 - Optional fields in PivotalTracker
Issue -
State: open - Opened by paul-mesnilgrente over 5 years ago
- 2 comments
#37 - Optional fields in PivotalTracker
Issue -
State: open - Opened by paul-mesnilgrente over 5 years ago
- 2 comments
#37 - Optional fields in PivotalTracker
Issue -
State: open - Opened by paul-mesnilgrente over 5 years ago
- 2 comments
#36 - Feature/smtp nodemailer
Pull Request -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#36 - Feature/smtp nodemailer
Pull Request -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#36 - Feature/smtp nodemailer
Pull Request -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#36 - Feature/smtp nodemailer
Pull Request -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#36 - Feature/smtp nodemailer
Pull Request -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#36 - Feature/smtp nodemailer
Pull Request -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#36 - Feature/smtp nodemailer
Pull Request -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#35 - Build Error for @datafire/gisgraphy: Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
Issue -
State: closed - Opened by maurusrv over 5 years ago
- 1 comment
#35 - Build Error for @datafire/gisgraphy: Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
Issue -
State: closed - Opened by maurusrv over 5 years ago
- 1 comment
#35 - Build Error for @datafire/gisgraphy: Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
Issue -
State: closed - Opened by maurusrv over 5 years ago
- 1 comment
#35 - Build Error for @datafire/gisgraphy: Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
Issue -
State: closed - Opened by maurusrv over 5 years ago
- 1 comment
#35 - Build Error for @datafire/gisgraphy: Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
Issue -
State: closed - Opened by maurusrv over 5 years ago
- 1 comment
#35 - Build Error for @datafire/gisgraphy: Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
Issue -
State: closed - Opened by maurusrv over 5 years ago
- 1 comment
#34 - Slack integration "as_user" fails
Issue -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#34 - Slack integration "as_user" fails
Issue -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#34 - Slack integration "as_user" fails
Issue -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#34 - Slack integration "as_user" fails
Issue -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#34 - Slack integration "as_user" fails
Issue -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#33 - SMTP integration friendly names
Issue -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#33 - SMTP integration friendly names
Issue -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#33 - SMTP integration friendly names
Issue -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#33 - SMTP integration friendly names
Issue -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#33 - SMTP integration friendly names
Issue -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#33 - SMTP integration friendly names
Issue -
State: closed - Opened by rion18 over 5 years ago
- 2 comments
#32 - Gitlab "API V3 is no longer supported. Use API V4 instead."
Issue -
State: open - Opened by eriksape over 5 years ago
- 4 comments
#32 - Gitlab "API V3 is no longer supported. Use API V4 instead."
Issue -
State: open - Opened by eriksape over 5 years ago
- 4 comments
#32 - Gitlab "API V3 is no longer supported. Use API V4 instead."
Issue -
State: open - Opened by eriksape over 5 years ago
- 4 comments
#32 - Gitlab "API V3 is no longer supported. Use API V4 instead."
Issue -
State: open - Opened by eriksape over 5 years ago
- 4 comments
#32 - Gitlab "API V3 is no longer supported. Use API V4 instead."
Issue -
State: open - Opened by eriksape over 5 years ago
- 4 comments
#32 - Gitlab "API V3 is no longer supported. Use API V4 instead."
Issue -
State: open - Opened by eriksape over 5 years ago
- 4 comments
#31 - Update openapi.json
Pull Request -
State: closed - Opened by dmonaldo over 5 years ago
- 1 comment
#31 - Update openapi.json
Pull Request -
State: closed - Opened by dmonaldo over 5 years ago
- 1 comment
#31 - Update openapi.json
Pull Request -
State: closed - Opened by dmonaldo over 5 years ago
- 1 comment
#31 - Update openapi.json
Pull Request -
State: closed - Opened by dmonaldo over 5 years ago
- 1 comment
#31 - Update openapi.json
Pull Request -
State: closed - Opened by dmonaldo over 5 years ago
- 1 comment
#31 - Update openapi.json
Pull Request -
State: closed - Opened by dmonaldo over 5 years ago
- 1 comment
#30 - [ Basecamp3 ] Missing replies in inbox_forwards's endpoint
Issue -
State: closed - Opened by 0xjjpa over 5 years ago
- 4 comments
#30 - [ Basecamp3 ] Missing replies in inbox_forwards's endpoint
Issue -
State: closed - Opened by 0xjjpa over 5 years ago
- 4 comments
#30 - [ Basecamp3 ] Missing replies in inbox_forwards's endpoint
Issue -
State: closed - Opened by 0xjjpa over 5 years ago
- 4 comments
#30 - [ Basecamp3 ] Missing replies in inbox_forwards's endpoint
Issue -
State: closed - Opened by 0xjjpa over 5 years ago
- 4 comments
#30 - [ Basecamp3 ] Missing replies in inbox_forwards's endpoint
Issue -
State: closed - Opened by 0xjjpa over 5 years ago
- 4 comments
#29 - Error handled when error thrown while connecting to ldap server
Pull Request -
State: closed - Opened by shakya008 over 5 years ago
- 2 comments
#29 - Error handled when error thrown while connecting to ldap server
Pull Request -
State: closed - Opened by shakya008 over 5 years ago
- 2 comments
#29 - Error handled when error thrown while connecting to ldap server
Pull Request -
State: closed - Opened by shakya008 over 5 years ago
- 2 comments
#29 - Error handled when error thrown while connecting to ldap server
Pull Request -
State: closed - Opened by shakya008 over 5 years ago
- 2 comments
#29 - Error handled when error thrown while connecting to ldap server
Pull Request -
State: closed - Opened by shakya008 over 5 years ago
- 2 comments
#29 - Error handled when error thrown while connecting to ldap server
Pull Request -
State: closed - Opened by shakya008 over 5 years ago
- 2 comments
#29 - Error handled when error thrown while connecting to ldap server
Pull Request -
State: closed - Opened by shakya008 over 5 years ago
- 2 comments
#29 - Error handled when error thrown while connecting to ldap server
Pull Request -
State: closed - Opened by shakya008 over 5 years ago
- 2 comments
#28 - Integration for Evernote
Issue -
State: open - Opened by BharathNuke over 5 years ago
#28 - Integration for Evernote
Issue -
State: open - Opened by BharathNuke over 5 years ago
#28 - Integration for Evernote
Issue -
State: open - Opened by BharathNuke over 5 years ago
#28 - Integration for Evernote
Issue -
State: open - Opened by BharathNuke over 5 years ago
#28 - Integration for Evernote
Issue -
State: open - Opened by BharathNuke over 5 years ago
#28 - Integration for Evernote
Issue -
State: open - Opened by BharathNuke over 5 years ago
#27 - Integration with JIRA requires username and password
Issue -
State: closed - Opened by codecraf8 over 5 years ago
- 1 comment
#27 - Integration with JIRA requires username and password
Issue -
State: closed - Opened by codecraf8 over 5 years ago
- 1 comment
#27 - Integration with JIRA requires username and password
Issue -
State: closed - Opened by codecraf8 over 5 years ago
- 1 comment
#27 - Integration with JIRA requires username and password
Issue -
State: closed - Opened by codecraf8 over 5 years ago
- 1 comment
#27 - Integration with JIRA requires username and password
Issue -
State: closed - Opened by codecraf8 over 5 years ago
- 1 comment
#27 - Integration with JIRA requires username and password
Issue -
State: closed - Opened by codecraf8 over 5 years ago
- 1 comment
#26 - to field taken as array instead of array item
Pull Request -
State: closed - Opened by shakya008 over 5 years ago
- 2 comments
#26 - to field taken as array instead of array item
Pull Request -
State: closed - Opened by shakya008 over 5 years ago
- 2 comments
#26 - to field taken as array instead of array item
Pull Request -
State: closed - Opened by shakya008 over 5 years ago
- 2 comments
#26 - to field taken as array instead of array item
Pull Request -
State: closed - Opened by shakya008 over 5 years ago
- 2 comments
#26 - to field taken as array instead of array item
Pull Request -
State: closed - Opened by shakya008 over 5 years ago
- 2 comments
#25 - Integration with outlook calendar
Issue -
State: open - Opened by BharathNuke over 5 years ago
#25 - Integration with outlook calendar
Issue -
State: open - Opened by BharathNuke over 5 years ago
#25 - Integration with outlook calendar
Issue -
State: open - Opened by BharathNuke over 5 years ago
#25 - Integration with outlook calendar
Issue -
State: open - Opened by BharathNuke over 5 years ago
#25 - Integration with outlook calendar
Issue -
State: open - Opened by BharathNuke over 5 years ago
#25 - Integration with outlook calendar
Issue -
State: open - Opened by BharathNuke over 5 years ago
#25 - Integration with outlook calendar
Issue -
State: open - Opened by BharathNuke over 5 years ago
#24 - Adding "completed" parameter within todo query spec
Pull Request -
State: closed - Opened by 0xjjpa almost 6 years ago
- 4 comments
#24 - Adding "completed" parameter within todo query spec
Pull Request -
State: closed - Opened by 0xjjpa almost 6 years ago
- 4 comments
#24 - Adding "completed" parameter within todo query spec
Pull Request -
State: closed - Opened by 0xjjpa almost 6 years ago
- 4 comments
#24 - Adding "completed" parameter within todo query spec
Pull Request -
State: closed - Opened by 0xjjpa almost 6 years ago
- 4 comments
#24 - Adding "completed" parameter within todo query spec
Pull Request -
State: closed - Opened by 0xjjpa almost 6 years ago
- 4 comments
#24 - Adding "completed" parameter within todo query spec
Pull Request -
State: closed - Opened by 0xjjpa almost 6 years ago
- 4 comments
#24 - Adding "completed" parameter within todo query spec
Pull Request -
State: closed - Opened by 0xjjpa almost 6 years ago
- 4 comments
#23 - [ Basecamp3 ] Missing completed tasks in todo's endpoint
Issue -
State: closed - Opened by 0xjjpa almost 6 years ago
- 1 comment
#23 - [ Basecamp3 ] Missing completed tasks in todo's endpoint
Issue -
State: closed - Opened by 0xjjpa almost 6 years ago
- 1 comment
#23 - [ Basecamp3 ] Missing completed tasks in todo's endpoint
Issue -
State: closed - Opened by 0xjjpa almost 6 years ago
- 1 comment