epics | EBICS client for Ruby | REST library

The sample you linked uses a Subject as a trigger to inform the table to re-render.

Do that as well and it should work as expected.

Start Date and Finish Date fields are calculated if you create a project plan in Microsoft Project and then synchronize that plan with tasks that are stored in Azure Boards. These fields may not appear on the work item form, but they are calculated for those backlog items and tasks that are linked to backlog items. The values are read-only in backlog items and tasks, so you can not modify them.

If you want to set "Start Date" and "Finish Date" for a task, you could customize (need to use inherited process) two Date/Time fields, and add them in a group.

1. Go to inherited process, select Task work item, and hide the "Start Date" and "Finish Date" field:

1. Create two customized Date/Time fields:

1. Now you would be able to set Date/Time in Task work item:

You have to escape quotes inside quotes:

issueFunction in issuesInEpics("\"Parent Link\" = ABCD-28089 AND \"Requested Version\" = \"Release 3.3.0\"")

Or use single quotes instead:

issueFunction in issuesInEpics("'Parent Link' = ABCD-28089 AND 'Requested Version' = 'Release 3.3.0'")

Python's Requests does not support "Expect: 100-continue" ([1], [2]), and if you are communicating with a server that actually requires 100-continue for large posts (and it looks like that's the case), your best bet is to find a http library which supports it (for example libcurl/Pycurl)

it may not work to just manually add the Expect: 100-continue header to the Requests http-request either, as the client is supposed to send that header, then wait for a 100 Continue response, and THEN send the body, but when just adding the header to the request, that does not magically teach Requests that it has to "wait for the 100-continue response before sending the body", Requests will just immidiately send the body without waiting, so.. yeah, find a http library that actually natively support it. (like libcurl/pycurl)

.. and if you can be arsed, would be nice if you went to the relevant Requests feature request and voiced your support.

i want to change some parent links from the old epic to another epic.

Open the User Story->click the links tab->Select the parent link->click the button Remove link->click Add links->Existing item->select Links type Parent->enter another Epic work item ID->Click OK and Save&Close button to save it, then we could see the parent link has changed. Check the GIF below.

Is there a better way to organize the backlog when I have two different area paths and need easily identify which one a work item belongs to?

Method 1. Add "Area Path" as a Column.

Click Column Options at the top and Add "Area Path" as a clumn. Then you can see area directly at the page.

Method 2. Use queries.

Go to Boards/Queries. Create a query and set your Work Item Type and your Area path. Here is an example.

Then select "Tree of work items" in "Type of query".

You will find work items in a specific area arranged in a tree form.

Normally, if you follow the document "Bulk import or update work items using CSV files" to export and import work items between projects, there should not be any issue may cause the work items disappear in the project.

Please go to the Recycle Bin to check if these work items have been deleted in your project B. And navigate to Organization Settings > Auditing to check if there is any logs to show who has deleted these work items recently.

How do you organize your backlog list so that you can identify easily which PBIs are related to which Epic and Feature?

In Azure DevOps Backlogs, you can show Parents and Related Link Count as Columns.

Click Column Options to add columns that you need to show in the backlog.

In Boards, you can show Parents in the card.

Click the Settings button in the upper right corner. Choose Cards/Fields/Additional fields to add fields that you need to show in the card.

To show which PBIs are related to which Epic and Feature, you can use queries.

In JIRA you have different colors that identify the Epics but in Azure boards, all of them are the same icons.

You can set different colors for work items in Azure DevOps.

Click the Settings button in the upper right corner. Choose Cards/Styles. Here, you can set card color and title style for different work items according to the rules. Here is an example. I set the work items with priority 1 to light orange. The final result is shown in the picture above.

Most Redux Toolkit apis should not be called with manually specified generics.

By calling return configureStore(... you actually erase all information about middlewares from your store. Skip the generic, just call return configureStore(... and let TypeScript infer the correct types from usage.