Azure DevOps ticket styling: Setting a colour for reopened tickets - azure-devops

My team is using card styling to indicate delays on tasks in Azure DevOps.
There's a loophole that clears the colours if the tasks are changed from Active to New/Closed and pulled back into Active - it resets the colouring countdown.
Is there a way to indicate if a card has been previously activated, closed and reopened again without having to set a colour on all tasks that are pulled into Active from New?
Our current styling rules are as follows:
Activated Date <= #Today - 5
Work Item Type = Task
State = Active
your text Example as per image
I started with Changed Date instead of Activated Date but the counter reset when a comment was made in the ticket.
I also tried Closed Date but the colours clear out again when pulled back into Active.
I also tried Start Date but the colours reset every time it changes status, so it resets the count when Closed (would like this to stay the same as it was on Active before it was Closed)

Related

Changing Agent color based on queue waiting time

I am creating a DES model with an animation. I would like to show a change in color for agents that have been waiting in a queue for more than a certain time. One option I thought of is to use a timeout and change the color on exit of the timeout, but the problem with this approach is it may mess up the order of the agents in the queue.
Is there a way in AnyLogic to be able to model this?
Thank you.
you can use a normal event manually triggered... you can set that up in the event properties (mode: user control), so when an agent enters the queue you start the event doing agent.event.restart(timeout,TIMEUNITS);
and in the event you change the color of the agent
obviously this event has to be inside the agent

How do I add a column with a new status in Jira?

I've modified the board and added a column in Jira but there are no status for it and it doesn't show on the board, how to fix and have the new column show up on the board and work correctly ?
This has confused me several times so I'm documenting the steps here.
Go to Board Settings
Click on columns
Click 'Add column' to add the new column - Code Review in my case
You will notice however that the board say
This column will not show on the board without a status
You may also notice that the min/max values cannot be entered
So you (think) next go to Issue Types...
WRONG !
Actually you want to go to
Workflows
You'll see a workflow called something like Software Simplified Workflow for Project [..].
Click on the Actions edit link (the pen symbol)
Now you will be presented with a diagram showing the status'.
Click + Add status and add the new status, e.g. Code Review
Make sure you allow transitions from the other status (it is unchecked by default, so you should usually check it)
It is when you fail to do this that you can run into the 'can't drop ticket into column problem'
Next select the status category. Code Review was obviously "in-progress".
This allows for automatic ticket status transitions.
Arrange the new diagram to reflect the new status (this is for appearance in the diagram only).
Finally the last step is that you have to publish the change ('draft')
Now you can see the "unmapped status"
and you can move them into then new column
When you do all this, finally you can reload the board and see the new status!
Whew !!!

Scheduled pages report from AEM

Is there any way to view a report for all pages scheduled for activate later from AEM? I am able to see one report under Tools (Workflow Report) which shows the total count of "Scheduled Page/Asset Activation", but I want to see all page information about scheduled page activations including time for activation.
You can view all running workflow instances by navigating to
http://localhost:4502/libs/cq/workflow/content/console.html and clicking on the the Instances tab. Look for Scheduled Page/Asset Activation under the Workflow Model column. You can group and sort by that column.
If you want to search from within your code, you can find the resources waiting to be activated with these JCR-SQL2 or XPATH queries:
SELECT * FROM [cq:Workflow] AS s WHERE ISDESCENDANTNODE(s,'/etc/workflow/instances') AND s.[modelId] = '/etc/workflow/models/scheduled_activation/jcr:content/model' AND s.[status] = 'RUNNING'
/jcr:root/etc/workflow/instances//*[#modelId='/etc/workflow/models/scheduled_activation/jcr:content/model' and #status='RUNNING']
However, it sounds like what you want to do is create a custom report:
Navigate to http://localhost:4502/miscadmin.
Open Reports in the left pane.
Click New... > New Page... in the right pane.
Select the Workflow Instance Report template and give it a title.
Open the new page.
Drag Model from the sidekick into the parsys. The report should immediately populate.
Drag Payload from the sidekick into the title bar where Model already exists.
Click the dropdown arrow in the Model column, select Filter, equals and enter Scheduled Page/Asset Activation.
Drag Status from the sidekick into the title bar where Model and Payload already exist.
Click the dropdown arrow in the Status column, select Filter, equals and enter RUNNING.
You can drop in any other columns that you wish. You can save the report and set it up to create snapshots as well.
This will give you a report of pages scheduled to be activated. Unfortunately, it won't tell you the time that the page will be activated. In order to accomplish this you will have to create a new reporting column component.
Copy /libs/cq/reporting/components/instancereport/payloadcol into your apps folder renaming as something like scheduledcol.
Look at the scheduledcol node and notice the jcr:primaryType, componentGroup and sling:resourceSuperType; it's a regular CQ component.
Update the jcr:title property to Scheduled.
Update the scheduledcol/definitions/queryBuilder node's property property. You can go with either ./data/metaData/comment which gives you plain text or you can use ./data/metaData/absoluteTime which gives you the date and time in milliseconds when the activation will occur. Look at a workflow instance under /etc/workflow/instances/<date>/model_<number>/data/metaData and you'll see how the new component's queryBuilder property matches up.
Return to your report, refresh the page, and drag the new Scheduled component from the Sidekick onto your report.

Chronoforms 5 Date Picker in Multiplier Not Working

I'm using Chronoform's 5 Multiplier feature which is triggerd with an 'Add Another Student' button. Prior to the Multiplier, I have two datepickers. Within the Multiplier are two datepickers. The first set of datepickers (prior to the Multiplier) pops up the calendar, as it should. Within the Multiplier, the calendar does not pop up.
Both datepickers have indpendent fieldIDs. After asking Chronoforms regarding this issue, the answer I received was:
"You'd have to add custom code to run when the Add button is clicked and attach the datepicker to the new...input then."
I'm not sure what this means.
Has anyone successfully been able to use Chronoforms 5 to get the datepicker to work within a Multiplier? Users can enter in a date manually, but that's not user-friendly. I would prefer to try to get this working.

How can I make org-mode store state changes for a repeating task in a drawer?

Basically, I have a lot of tasks that are set to repeat and I like keeping records of what days they actually get done, but the recorded state changes don't collapse nicely. Is there some way to make emacs store them in a drawer or some other structure that's collapsible?
EDIT:
org-version 8.2.7
There is an option called org-log-into-drawer (doc here) to control this.
If set to non-nil, all state changes and notes will be added to a drawer.
You can even control the order in which changes are recorded with org-log-states-order-reversed.
More info in the manual.