YouTrack How to display sprint info in issue table - youtrack

I need to find a way to display info to which sprint issue is assigned in issues table.
Two possible ways I see:
Through List Settings
With automatic assign of tags to issue in Sprint №
Probably there are other solutions.
Solutions for YouTrack Lite is preferable.
List Settings in Issues
Tag in issue

Both options are valid. The most common one would be using the list settings though. The main idea here is to link a sprint to a specific field value. For example, you create a field called Sprint (or whatever you want), and this field's values correspond with your sprints. For that, boards have a special setting called Link Sprints to Values for Custom Field.
After that, all you need to do is to add this sprint field to the issue list.

Related

Podio Calculation field issue

We have an issue with a calculation field not always working. (We have about 5 calculation fields that are similar so same applies to all).
See in the attached example.
The Textbook item has a calc field 'Set Text'. One of the values in there is showing 'Null'.
Most of the time this works fine but in about 8% of the cases it has this null error.
See the other screenshot of the Aggregator item. The field that is being referenced there is correct.
To fix it we have to manually remove the relationship between the two items and then put it back again, to force the calculation to recalculate. This fixes the issue. So the problem does not seem to be the formula but rather the calculation being performed incorrectly.
The Aggregator items are created and joined to the Textbook item through the API.
This is a big issue for us as we use this value to post to our website so the manual fix is not a practical solution.
Podio support please advice what the issue is here
Aggregator
Null error
Without knowing too many details about your specific workflow and structure, let me offer some ideas:
Podio calculation fields can begin to act in strange ways if the original field is being referenced by calculation fields too many levels deep. What I mean by this is that if the original field that shows the Paper Code (or whatever that int showing null is) is being referenced through too many calculation fields, it can begin to cause problems in cases of updating and adding new items. This is most definitely a bug I've encountered with large-scale systems, but there are workarounds.
First off, I see that you have all of the pertinent non-concatenated fields at the bottom of your Aggregator app. Try manually concatenating those fields in the Textbooks app (where you're doing the result.push) instead of referencing the Web course text calc field exclusively.
If that doesn't work and you're proficient with the API, a longer workaround could be that after the automation runs, you wait a sufficient time (say 30 seconds) until the calculation field updates, have the API check for the text "null" in the calculation field, and refreshes the relationship fields if null is found.

Work Item Query Policy to check workitems match on merge

With our TFS 2015 source control we require developers to check-in changes against work items.
However, we've had a couple of instances where a developer has checked in against one work item within our development branch, but then when merging to our QA branch they've checked in the merged changes to a different work item. An example of this is where a bug has been created underneath a PBI, the changes in dev have been checked in against a task under the bug, but then merged to QA against the PBI itself. This causes us issues with traceability.
I've seen that it's possible to add a check-in policy of "Work Item Query Policy". I'm just wondering if there is a way to write a query that will determine if the work item of a check-in after a merge matches the work item of the source changesets? I'm not necessarily after the exact query (though it would be lovely if someone could provide one :) ), really I'm just wondering whether it's possible or not to have a query to do this - i.e. is the information available to queries in TFS?
You can't do this with the existing policies, you'd need to build a custom policy.
So, technically this is possible. You can access the VersionControlServer object through the PendingChanges object:
this.PendingCheckin.PendingChanges.Workspace.VersionControlServer
You can use that to query the history of the branch in question and grab the work items associated to the check-ins in that branch.
You can check the associated workitems to the current workitem:
this.PendingCheckin.WorkItems
You could probably even provide the option to auto-correct by adding the correct work items to the checkin upon validation.
One of my policies provides an example on using the VersionControlServer from a policy.

Sharing custom fields across TFS 2015 Update 1 work items

I am working adding some customization to TFS 2015 Update 1 work item templates. I have started with the bug template and have successfully mirrored that across multiple projects.
I now have to make changes to the feature template, those changes need to include fields of the same name due to queries that will be filtering on values in the custom field.
I am finding that I cannot resuse the custom fields from the bug in the feature template. I also cannot create a custom field for the feature template with the same name as that in the bug.
Is there anyway to do this? My custom field in the bug is named "Task Status" with a ref name of .task.status.
Is there any way of making this existing custom field usable across template types? My end users don't want to have to duplicate queries to obtain the same data from multiple work item types.
Thanks!
I cannot reproduce this issue at my side, list my steps for your reference (I'm doing it from TFS Power Tools\Process Template Editor):
Add "TaskStatus" field for Bug and save it:
Add "TaskStatus" field for Feature and save it(The setting is the same):
Then I just need one query for both Bug and Feature work items:

How do I list all 'Urgent' priority bugs across all projects in Redmine?

We're migrating from Bugzilla to Redmine and there's one feature of bugzilla which I'm unsure how to replicate in Redmine.
Is there any way to list all the bugs / features of a specific priority across all projects?
We used to use this mechanism to identify what bugs / features to assign next to developers. If listing all urgent bugs doesn't work in Redmine, perhaps there's a different way of working which could be used instead?
This is easy:
Go to https://your.redmine.domain/issues?set_filter=1 : This should clear any current filter criteria and display all open issues across all projects the currently logged user has access to.
Select your filter - in this case, add a filter for Priority, and hit apply
You may save this filter by clicking on Save: This will allow you to access to this filter quickly without configuring it every time. You may also choose grouping criteria as well as the columns to display.

eclipse preference - where and how to store

I'm developing an Eclipse-Plugin which has it's own preference page.
First question: Is it possible to store these preferences workspace independent? Instead, I'd like to store it for the Eclipse installation. If yes, how?
Second question: I'd like to add a table to my preference page which has one column and a checkbox for each row (to sign the row entry as active or inactive). The column should contain file locations and/or urls of text files. So for the one preference setting, I'd have to store a list of location and the information whether it's active or not. Which would be the best way (which delimiters?)?
The Eclipse Preference service do support a scope context for the preference store. You can either store preferences in an Eclipse project, in the workspace, in the instance installation or into a custom scope.
Please refer to the following FAQ for more information on Eclipse Preference Scope: http://wiki.eclipse.org/FAQ_What_is_a_preference_scope%3F
For the way to store your table preferences, IMO there is no real best way to do it. I would say that you can serialize the whole table into a string using a specific pattern/matcher to parse it.
For instance, you can use the following format:
your.table.preference=(url1,boolean);(url2,boolean);(url3,boolean)