I get this error when I move the issue from In Progress to Done.
Workflow jetbrains-youtrack-scrum reports error: Cannot find State [Done]
Contact project admin admin
This was fine before, but has started behaving differently ever since the issue was also added to two boards.
Both the boards have "Done" as a valid status. What can be the problem?
This workflow may fail with such an error if it is not possible to set 'Done' state to a parent issue.
Thus, most probably, this particular issue is a subtask of some other issue from another project, which doesn't have a 'Done' state in its 'State' field values set.
Related
I am trying to configure planning tools to use the Backlog and Board features in TFS 2015. I am getting 7 warnings and 2 errors when I try to configure features and click the Verify button. Years ago a developer was playing with the work item types but none of the work the developer did is valid. It's preventing me from configuring features. Here is the list of warning and errors when trying to configure features.
[Warning]TF400609: Cannot add the action
'Microsoft.VSTS.Actions.StartWork' to the work item type 'Task'
because the state 'New' does not exist.
[Warning] TF400609: Cannot add the action
'Microsoft.VSTS.Actions.StopWork' to the work item type 'Task' because
the state 'New' does not exist.
[Warning] TF400609: Cannot add the action
'Microsoft.VSTS.Actions.StartWork' to the work item type 'Bug' because
the state 'New' does not exist.
[Warning] TF400609: Cannot add the action
'Microsoft.VSTS.Actions.StopWork' to the work item type 'Bug' because
the state 'New' does not exist.
[Warning] VS402404: Bugs On TaskBoard: Bug does not have the
Microsoft.VSTS.Common.Activity field defined. Some charts will not
include these work item types.
[Warning] VS402404: Bugs On TaskBoard: Bug does not have the
Microsoft.VSTS.Scheduling.RemainingWork field defined. Some charts
will not include these work item types.
[Warning] TF400607: Category 'Microsoft.HiddenCategory' will be
overwritten.
[Error] TF400654: Unable to configure Planning Tools. The following
element contains an error: RequirementBacklog/Columns. TF400529: This
element defines the columns that appear on the backlog. You must set
all values to fields that exist in at least one of the work item types
belonging to the category. The following fields do not exist in any
of the work item types: Microsoft.VSTS.Common.ValueArea.
[Error] TF400654: Unable to configure Planning Tools. The following
element contains an error: BugWorkItems/BugWorkItems. TF400506:This
element defines the states for work items that represent Bugs or
Defects. Each state must exist in at least one of the work item types
that are defined in: BugWorkItems. The following states do not exist
in any of the work item types: New.
I am wondering if I can upload the "out of the box" agile process
templates for TFS 2015.
On a side note, when I download the Agile Process Template using the Process Template Manager in Visual Studio 2013 and then immediately
try to upload the same templates (without any changes) I get the following error:
Exception Message: TF237070: Importing the definition failed. The
definition you are trying to import did not validate against the
schema. Edit the definition, then try toimport it again.
So I am not even sure I will be able to upload the "out of the box" agile process templates.
Thanks in advance for any insight into my issue.
First, to manage the process template. You should need to open the same version of Visual Studio or Team Explorer as the on-premises TFS that you connect to. For example, if you connect to a TFS 2015 instance, you must connect from Visual Studio 2015 or Team Explorer 2015.
According to the error info TF400654, this error is mentioned in MSDN link Resolve errors received when configuring features, please try the related resolution:
Export process configuration using witadmin
exportprocessconfig.
Change the States elements and add the missing field or state to match your work items states.
Then export categories and all categories matches your workflow
requirements.
Finally import them after changes.
Some times the ActivityFeeds.Plugin.ActivityClose plugin gets registered on the wrong entity and it stops me from creating new records for that entity.
It usually happens after I register a new plugin with the Plugin Registration Tool.
What is the cause? and how do I solve it?
I haven't found the cause, or how to solve it for good, but to make it work again is simple:
Log into the Plugin Registration Tool.
Select View->Display by Entity(Ctrl+Shift+E).
Expand the entity you are having trouble with.
Expand (message)Create.
Finally select the step for ActivityFeeds.Plugin.ActivityClose and Disable it.
--(Don't Unregister it [in case something breaks])
disable/unregistered the following like steps in plugin ActivityFeeds.Plugins.ActivityClose
ActivityFeeds.Plugins.ActivityClose: Update of any Entity
CAUSE
This kind of steps is registered unintentionally when we do some thing like below in screen shots:
Following is the plugin ActivityFeeds.Plugins.ActivityClose, you can see there is no step registered for this plugin.
Registered an assembly.
Right click on assembly name not on plugin, select registered new step.
Just enter update in message field and then press enter
you can see a step ActivityFeeds.Plugins.ActivityClose: Update of any Entity is added to ActivityFeeds.Plugins.ActivityClose
A SCORM Question regarding how I invoke Rollup (macro?) in Saba.
I have a SCORM manifest which contains two SCOs.
The second is only available when the first is completed by having a preConditionRule (similar to the SCORM/Rustici Golf Examples).
When a Delegate is successful with the first SCO I set 'cmi.completion_status' to 'completed' and 'cmi.success_status' to 'passed'.
The second SCO is a test so I set 'cmi.score.raw', 'cmi.score.scaled' and 'cmi.completion_status' to 'completed'.
As I have a 0.8 in the second SCO's primaryObjective the Saba LMS is able to evaluate a test status of 'passed' or 'failed' on exit of the test.
When I exit this Learning, Saba displays that both SCORM Items have been passed and completed.
However, the 'Content Attempt Status' is always 'Suspended'. This initially pointed to some of my JS interactions as I was using 'cmi.suspend_data' to store some info on a SCO. Even though this is disabled and even when I have a single unrelated SCO, the 'Suspended' Status is still set.
So, I still don't seem to get a Rollup (never seen one) and it is somehow to do with this 'Suspended' State I am somehow setting or not resolving.
One question is whether I should be setting 'cmi' 'completion_status' and 'success_status' in my interactions with the SCORM API at 'Object' Level (cmi.objective.n.success_status') rather than 'cmi.success_status' or both? I've tried both but am not certain which is right. I think it may depend on the Manifest.
Has anyone managed to get Saba to Rollup (Set Learning Assignments' 'Completion Status' so it no longer displays 'Not Evaluated') in this way?
My Manifest file seems ok, the Saba Player's Table of Contents shows the green light for each completed SCO in the Package but until I resolve the Status of 'Suspended', I am a little stuck.
I 'cmi.exit' both SCOs in the 'normal' way.
I am using Pipwerks Wrapper on this too but it seems to be ok.
Does this all point to the API, to the Manifest or to something I'm not setting up on Saba?
Thanks.
You're right that setting cmi.exit to 'normal' should not reflect suspended. Unless another call is being made on unload of the SCO, typically a window.unload or otherwise.
I've got a bookmarklet up on http://goo.gl/MXJVNM, but it sounds like with those events happening so fast you won't be able to trap the status without having another logging mechanism.
You could always offload the test to the cloud.scorm.com to see if it performs the same way, and you'll get a rich set of logs to review.
Mark
I have created a custom state machine workflow.When I am submitting the request using info-path form,workflow get started ,but no task is created in task list.
I tried to do manual entry in task list ,but still no item is added to task list.
How can I fix this problem? Is there any problem with my task list?
Generally, in software design, which of the options below is preferred when there is a problem or error with a resource such as a database or file?
Show an error message
Do not show an error message and act as though the resource was empty (eg. do not populate a GUI component)]
For example, should the user see an empty DataGrid following which they complain, or should there be an error message? Which is better?
I don't see this as an either/or. Also, we need to consider all "users" of the system.
First consider the UI. Let's consider a contrived general case: you are populating a UI by calling a service which in turn uses a couple of of databases (for example a "current data" and an "historic data") database.
There are at least these possibilities:
It all works, data is retrieved
It all works but as it happens there's no data for this particular query
Can't reach the service
Service is invoked, but one database is down
Service is invoked, but both databases are down
Then also consider your application's semantics. Can your applciation procede in a "degraded" mode if all the data cannot be retrieved? For example, we can't query the history but that doesn't stop us creating a new item.,
Now also consider the roles here. There's the person using the UI, there's also support and maintenance people who need to know about and fix problems.
My general rules:
First Failure Data capture: Whichever component first detects an error should log it in some detail. So, service up, database down the service should log the problem. Service down, the UI should log the problem. This log should be a technical record targeting the support roles.
UIs should be tolerant: if at all possible run in a degraded mode. So if the service is down but (for example) local working is possible put up an empty screen and continue. BUT ...
Always indicate a problem: The "no data for this query" and "databases unavailable" cases may both result in an empty screen. The user needs to know the status of the display, is it showing complete information, partial information (eg. because one DB is down) or is no information available (eg. service or both dbs down). So have a "Status" field somewhere on the screen. Giving messages such as
Historica Data not currently available
or
There are problems retrieveing
information, if these persist please
contact support ...
There are some pitfalls to each of the options
Showing error message
This is specially helpful when your application is in testing stage or public testing. Also when clients meets an error, he or she can copy down the details and forward to you.
However sometimes this error message gets very ugly (call stacks and so on - remember ASP.NET?) and it becomes so large that it becomes difficult for clients to copy down the details.
Do not show error message and act as though nothing happened =)
This is useful when you don't want error messages to cog up your software UI design. But be reminded that it becomes difficult and further error prone when clients can't differentiate between an actual error, or really nothing on the GUI. The error stays there and nothing gets fixed.
My stand
Get the best of both worlds. In fact most modern applications how have a very good error handling process. I'll take the example of Mozilla Firefox 3.
A deadly error occurred and Firefox crashes
Error is captured and stored into a file as a form of error report
Error Reporting Application pops up apologizing to the user
Ask the user if the user want to send the error report to the software dev team
Then ask the user if want to restart the application
Or if the error is a warning or of lesser severity:
Show a simple error code and tell the user that there's the error with that action. Something like: "Error 123 at RequestSalary() Line 2"
The practice I usualy use is:
If the error didn't happen due to user error, then you should try to handle the error quietly.
If the error occurred because of some external problem (such as no internet connection) then you should alert the user.
IMO you should show a message (albeit a user friendly one and not something like "java.io.IOException: Connection timed out".) You could have a message box telling the user that an error occured while getting the data and provide helpful tips like: Trying after some time, check network cable, etc.
Also allow user to report that error to you (error reporting build into the app) that will send you the actual error and stack trace.