Databases
StackOverflow2013
Usersdbo
USBrian Mueller
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USBrian Mueller
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. POJIRA implementation for process control and scrum
      singulars
      1. PTQuestion
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COOn the second response. Epics, we've tried epics. I'm finding them to be a bit limited and I'm not sure about the flow of items in the epic. For example, all items in an epic are not grouped together on the board. That is no good for us. When we used a whiteboard we would group them either by drawing lines around grouped items or by using the same color post-it notes for grouped items. Both were very good visual indicators of the whole process. As with above on the columns and sub-tasks. That method worked well for indicating who had the next step too.
      singulars
      1. PO
      1. USBrian Mueller
    2. COI'm not sure I understand the first item of the response. Pending in our setup basically means no action has been taken (open/new). Awaiting Action indicates that someone has put some effort into it but perhaps it's stalled (waiting for support to update us with steps to reproduce, waiting on a customer to call back to provide more details on a feature request, etc). We use separate sub-tasks currently because we want to provide visibility as to the steps. Part of my question was "is that best". I don't see any description of how it is not best in your response.
      singulars
      1. PO
      1. USBrian Mueller
    3. COI implemented this solution and did away with my DynamicContractResolver. This seems to be working very well and has the added bonus of being more readable, more understandable and giving me some added flexibility to have such things as "required return fields" and such. Thanks for the assistance.
      singulars
      1. PO
      1. USBrian Mueller
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload