I have a problem with FooterRow in Vaadin 14 and it's related to my case that I want to remove some already added FooterRows in my grid and append others but that seems doesn't work. I've tried with collection methods that getFooterRows() provide like removeAll, clear, and remove by iterating them one by one but that doesn't work. I've seen in the Github issue: https://github.com/vaadin/flow-components/issues/1538 that there is a conversation regarding it but there is not having an answer? Could someone know is there a way to do that?
Adding a PDF-Viewer tab to present/show a Sharepoint document has been working before.
I've tried this in January and it seemed to be an easy task - just get the DriveItem ID and URL (from GET /groups/{group-id}/drive/items/{item-id}) and edit the sample from the API Reference with these values (https://learn.microsoft.com/de-de/graph/teams-configuring-builtin-tabs#word-excel-powerpoint-and-pdf-tabs).
Now, that i want to use this, it doesn't work anymore ;-( The tab is created, added to channel, the name of the file shows BUT there is no document!!! What am i missing? Has the format changed? Has someone lately gotten this to work???
Please let me know, how! ;-)
ps: there is no description of the property "entityID" that makes any sense, can anyone explain it?
result in teams
Got the answer, was a Syntax problem!
The "contentURL" property needs to be unescaped (in this case the "%20"). It is that simple after all ;-)
Also i found out, the "entityID" property has no meaning for the File used. It can be "null" actually! I still use the ItemID i got from the DriveItem of the File.
For unescaping i used:
string contentUrl = Uri.UnescapeDataString(webUrl);
If it wasn't for this post I would have not gotten it figured out, so thank you!
For me I ended up having to make entityID null, just unescaping the contentURL didn't do it for me alone.
Thanks for your comment. leaving entityID null fixed my isse also.
I opend an issue to have the docs fixed!
I am using JSCS to validate my code and I have requireDotNotation set to on for all my code base, but for a specific part of code I need to disable this rule.
Basically I would need to do something similar (example working for JSHint) but for JSCS:
/*jshint sub:true*/
//some code here
/*jshint sub:false*/
I was able to solve this issue using the following code:
//jscs:disable requireDotNotation
//some code here
//jscs:enable requireDotNotation
I am adding this answer hope can help others.
In org-mode, I have defined a figure+caption like this:
#+CAPTION: My great figure
#+LABEL: fig:myfigure
[[myfigure.png]]
How do I write "See figure [myfigure]"? I've found the following syntax:
See figure \ref{fig:myfigure}
but this looks ugly in the source file. In particular, you cannot use it for actually jumping to the figure.
You actually don't need '#+NAME', it works fine if you use '#+LABEL', which won't break your short-caption for list of figures.
Orgmode does now offer a 'jumpable', enumerated or link with name of your choice in the exported (latex, html) text if you link with:
see figure [[fig:myfigure]].
or
see figure [[fig:myfigure][figurenameintext]].
I would have added this as a comment, but I don't have the reputation yet.
--
In response to your comment (still can't comment): you do need the '#+NAME' for it to jump within the .org source file; as mentioned in the manual, and i also just confirmed that works. Not sure about the short-captions in the latest version.
With a very recent org-mode, you can use #+name:, see:
http://thread.gmane.org/gmane.emacs.orgmode/62644/focus=62646
#+CAPTION: My great figure
#+LABEL: fig:myfigure
#+name: fig:myfigure
[[test.png]]
See figure [[fig:myfigure][test]].
This works for me to jump from the link , but has no effect when exporting, I'm afraid...
How to write query that will select only issues resolved by me.
I have found some old post that says its no possible, but it might have changed.
Use next JQL:
status was resolved by "username"
In 4.4 this seems to work:
status was "Resolved" by currentUser()
More details can be found here.
The answer most often given is to use JQL for something like
status was Resolved BY currentUser()
While all fine and good, this will give you back all the issues that you have ever resolved. That is, if you resolved issue FOO-1966 and then it got reopened and someone else resolved it again it is still an issue that was resolved by you.
Here's a better way to do this in JIRA 6 and later (including JIRA onDemand).
Create a custom field called "Resolver". Make it a person field but do not add it to any forms (unless you really want to).
Edit your workflow and add a post function to the resolve issue transition in your workflow. Make the action "Update custom field" and set the Resolver to %%CURRENT_USER%%.
Publish your workflow.
Now whenever someone resolves an issue using that workflow, the Resolver field will get set to the current user. Now the Resolver field is semantically "last resolved by".
As an added bonus, you can use the value in the Resolver field to reassign issues back to the person who resolved them when they get reopened. I'll leave this as an exercise to the reader. :-)
You can use this JQL query:
"Resolved by" = currentUser()
(I just verified this in v4.1.2#531 on a standalone version)
There is also a plug in you can use in older versions:
https://studio.plugins.atlassian.com/wiki/display/JQLT/Home
None of the above worked for me on JIRA (v4.1.2#531)
However, his works:
"Resource" = currentUser() AND (status = Fixed OR status = Closed OR status = "No Change Required") ORDER BY updated
You can use the WAS operator:
JIRA - Advanced Searching : "The "WAS" operator is used to find issues that currently have, or previously had, the specified value for the specified field"
Example: status WAS "Resolved" BY currentUser()
For JIRA v6.3.4, this worked for me:
"Resolved By" = currentUser()
As far as I can tell, search for resolved by me and more generally, for status changes, is not possible until at least JIRA 4.2.1 (the version I'm using now).
Search and JQL enhancements outlined in 4.3 and 4.4 release notes look like the move in the right direction (WAS operator) but I'm not holding my breath.
None of the above solutions worked for me. I started adding a label to all my issues to resolved_by_kishore, then in advanced search, I'm using lables=resolved_by_kishore. It's working fine.
project = prohjectname AND status was "Resolved" by username and resolutiondate >= '2014/01/08'
and its variants exists in jql now
i am not sure whether they existed at the time question was asked.
i am adding this answer so that if anyone comes here can find the answer
I guess you can use this
status in (resolved) AND component = COMPONENT_NAME AND assignee in (currentUser()) AND resolved > -1d
but the new thing here resolved > -1d this to get the issues that are resolved me in this day
resourses: https://community.atlassian.com/t5/Jira-questions/JIRA-4-4-search-filter-how-to-find-issues-resolved-in-last-seven/qaq-p/77326
The values used in Status can vary (e.g. Resolved, Closed, Done, ...) so it is not reliable to use.
Instead, use resolution:
resolution changed from EMPTY by currentUser()
Using = EMPTY seems to work for searching for empty custom fields with newer versions of Jira