[JBoss JIRA] (JBDS-1504) allow users to create cases from JBDS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1504?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen reassigned JBDS-1504:
-----------------------------------------
Assignee: Alexey Kazakov (was: Max Rydahl Andersen)
Bulk moving any issue assigned to me directly to Alexey for his new role.
> allow users to create cases from JBDS
> -------------------------------------
>
> Key: JBDS-1504
> URL: https://issues.jboss.org/browse/JBDS-1504
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: integration
> Environment: All
> Reporter: Andrew Hecox
> Assignee: Alexey Kazakov
> Fix For: LATER
>
>
> user-story: as a JBoss customer, I can create a case with support from JBDS so that I can easily get help solving the problem I'm working on in my editor
> notes: I think something which allowed a user to create a problem description, as well as send any applicable files, would be a good value add to JBDS. We have a public, stable, API for this:
> https://access.redhat.com/knowledge/docs/Red_Hat_Customer_Portal/
> we may deprecate some schema items in the next month or two, but otherwise it's locked in place for the next 7+ years. This functionality presumably would only be in the productized version, unless it was replaced with JIRA integration (or comparable)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-15246) JQuery Checkboxes have broken CSS layout on desktop browsers
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15246?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-15246:
-------------------------------------------
Assignee: Alexey Kazakov (was: Max Rydahl Andersen)
Bulk moving any issue assigned to me directly to Alexey for his new role.
> JQuery Checkboxes have broken CSS layout on desktop browsers
> ------------------------------------------------------------
>
> Key: JBIDE-15246
> URL: https://issues.jboss.org/browse/JBIDE-15246
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.1.0.CR1
> Reporter: Karel Piwko
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
> Attachments: browserSim.png, chrome.png, firefox.png, int.png, jquery-mobile-checkboxes-desktop.png
>
>
> JQuery Mobile palette does render properly on desktop browser (internal browser, chrome).
> How to reproduce:
> 1/ Create mobile example from JBoss Central
> 2/ Add "Checkboxes" from JQuery Mobile palette
> 3/ Deploy and open on desktop
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBTIS-796) Unify versions of BPMN2 plugins
by Robert (Bob) Brodt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-796?page=com.atlassian.jira.plugin.... ]
Robert (Bob) Brodt commented on JBTIS-796:
------------------------------------------
The o.e.b.editor plug-in belongs to the MDT BPMN2 Metamodel project, a completely different animal than the BPMN2 Modeler. Hence, the different versions. FYI, This editor is generated by the EMF ecore utility and is required for BPMN2 model support.
> Unify versions of BPMN2 plugins
> -------------------------------
>
> Key: JBTIS-796
> URL: https://issues.jboss.org/browse/JBTIS-796
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: BPMN2
> Affects Versions: 4.3.1.Final
> Environment: JBDSIS 9.0.1.CR1
> Reporter: Tomáš Sedmík
>
> I noticed there are BPMN2 plugins in two versions. For example:
> - org.eclipse.bpmn2.editor - 1.2.1.Final-v20160218-1950-B212
> - org.eclipse.bpmn2.modeler.core - 1.2.4.Final-v20160330-1625-B110
> [~bbrodt] Is that correct? IMHO all plugins of a single component should be in the same version.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22603:
---------------------------------------
[~adietish] I would like to address this issue ASAP. It's not annoying only from usability and user-friendliness, but this is serious issue for automated tests, I can say blocking one.
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Priority: Critical
> Labels: explorer, openshift_v3
> Fix For: 4.4.x
>
> Attachments: watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22667) Automation of manual test case in batch integration tests, Reference check
by Ondrej Dockal (JIRA)
Ondrej Dockal created JBIDE-22667:
-------------------------------------
Summary: Automation of manual test case in batch integration tests, Reference check
Key: JBIDE-22667
URL: https://issues.jboss.org/browse/JBIDE-22667
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: qa
Affects Versions: 4.4.x
Reporter: Ondrej Dockal
Assignee: Ondrej Dockal
Based on not automated polarion test case: JBDS-5994 - Search for artifact references
which is covering this features: Check that it is possible to find references for artifacts in job.xm file. See JBIDE-19507 for more details.
Should include this test cases:
Check references for artifacts (also use custom name)
Check references for properties (also use custom name)
Check references for exceptions
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22603:
-------------------------------------
Fix Version/s: 4.4.x
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Priority: Critical
> Labels: explorer, openshift_v3
> Fix For: 4.4.x
>
> Attachments: watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months