Is there a possibility to assign a number of milesstones to their respective components?
The idea is a following:
We've got components [A,B,C].
Component A has milestones [1,2,3]
Component B has milestones [4,5,6]
Component C has milestones [7,8,9]
On a "New ticket" page you can choose any milestone for any component.
The task is to have an opportunity to strictly assign milestones to components and view statistic based on this structure.
Any ideas?
To answer your question the task needs to be clarified and detailed a bit more.
Being able to assign only appropriate milestones, you'll have to enforce input order:
component
milestone (from filtered list)
So you'll need to conditionally hide the milestone input field, until a component has been selected.
After selecting the component you'll need to fetch an updated milestone list.
All that has to be done repeatedly, if you change the component before submitting the new ticket. And to not leave the /newticket page you'll even need to do page updates by back-ground requests (ajax style) that requires JavaScript.
You did not tell anything special about statistics, so I assume it could be done by a custom report the common way.
I know of a Trac plugin that is getting close: TracTicketChainedFieldsPlugin, but might still need some work to be done.
This sounds like a job for the Subcomponents Plugin. This will allow you to organize your components into a tiered structure, which makes it easy to do the sort of strict grouping that you are looking for. This doesn't have anything to do with milestones, though (it does everything using only components). If you strictly need to use a combination of milestones and components for some reason, then this might not work for you.
I think you want to use 'component' in the meaning of project, and you want to assign milestones for your certain projects.
You should rather install SimpleMultiProjectPlugin which is also able to map components, milestones and versions to certain projects.
Related
Or developers need the Work Item forms as designed for our agile process, but we'd like our regular users to be able to add new bugs and user stories using a simplified form, where a lot of fields are removed and some have team specific default values.
How can this be done?
The closest match I've found so far is templates, where field defaults can be defined, but the form that's used/displayed is still the large cluttered one. Being able to use the template link to land directly on a pre-filled form is a step in the right direction, though.
Azure DevOps allows you to modify your process template and add new work items to your project. You can find the documentation to do this here.
Go to Organization settings for your account --> Process --> Create an inherited process from your process template --> New Work Item Type.
You can then define the fields you want and the layout of the template.
Something else that could be useful in your scenario is the Test and Feedback Extension. This is a simple browser plugin that lets users explore feedback requests and file comments and bugs.
I'm looking to create a nice dashboard in VSTS with a set of relevant charts for my collegues so they can keep track of things.
We have a project for keeping track of it operations tasks. In this project we've created different Features for different departments of the company.
Is there a way to filter the user stories by parent/feature so that I can make different charts for different departments? I've managed to create a "Work items and direct links" query that actually only outputs the User stories in one feature, but such queries can not be used in charts unfortunately.
Other workarounds would be acceptable too.
There is a Work Item Visualization extension that you can check whether it meets your requirement (Can highlight specified work items).
Another way is that you can custom a dashboard widget or other extension to display the result: Add a dashboard widget.
There are many extension samples that may benefit you: vsts-extension-samples
For the construction of an extensive list of links, since the source page is a thematic portal, I am looking for a suitable EXT., Which also runs under TYPO3 7.6 LTS.
it if the list of links to a permits the use of categories and multiple categorization of links is possible would be nice. should Weiterrhin the links are described not only the destination address and an alias but here should still an outline of the target page (possibly with photo) be possible.
Additional functions such as proposing links by users, reporting broken links or even a User Voting would nice additional features.
There were times the Modern Linklist, but they were no longer being developed for TYPO3 <6.x.
Is there perhaps somewhere an alternative or as one might like to vorhnandenen solutions might realize? It would be nice of course, without any programming knowledge, since I'm not a programmer.
P.S .: It is not about building a spam list but high quality links with topics relating to the original page.
As this seems to be a straight forward usage you could try to build that extension by yourself with the ExtensionBuilder.
just build up the records neccessary for your data. and let the EB generate all usefull actions: list & show, even create, edit, delete in FE would be possible.
Afterwards you just need to edit the generated fluid templates.
these links may help:
Overview
EB manual
small remark: if you want the newest code state, use the EB from git instead of TER
I`m not aware of an existing extension for it but it could be a good project to learn extbase / fluid.
You should also take a look at
typo3/sysext/fluid_styled_content/Resources/Private/Partials/Menu
and
typo3/sysext/fluid_styled_content/Classes/ViewHelpers/Menu
Fluid Content contains everything you need to create a list like that, you "just" have to combine the necessary bits and pieces.
You can do a lot with TYPO3 core functionality: there is a page type "external URL", pages can have categories by default, there are plenty of menu options (TypoScript HMENU, menu content elements, Fluid menu Viewhelpers). The Linkvalidator can periodically check all links and report broken links.
For suggestions you could add a form. Powermail for example can also store submitted info in database records, so your visitors could prepare page records (they are hidden until you make them visible).
We are trying to use GitHub for issue tracking in one of our projects and while its very simply to use, we aren't sure its powerful enough at the same time to fulfil our needs to organize our issue management since we can't find a way to customize it.
Question: Is it possible to add custom attributes in GitHub for issue tracking, search/sort and export the list of issues with those attributes? For example, we'd like to add and use following attributes:
External Issue ID: There is an external list of issues/change requests maintained by a separate group that we need to associate
our issues with and need a field to specify the external issue ID.
Priority: so that we can easily discuss and prioritize what we want to tackle first
Severity: to identify impact on the system
Type of Issue: Bug, Change Request, New Requirement
Class: Performance, Security, Function, Compliance etc.
Source: to track whether issue was reported by a specific customer (which could be in hundreds), end user, internal team,
partner etc.
Date Opened: I think this is maintained internally by GitHub but not exposed anywhere in the UI
Date Closed
etc.
We understand some of these can be implemented with labels but there would be too many of them to assign and they do not allow exclusivity (for example you can only specify one priority - high, medium, or low assigning - to an issue)
Any ideas if and how this can be implemented in GitHub?
If not, any recommendations?
Thanks!
As you mentioned already, this so far is only done by using labels, for example the way i do priority is having multiple labels:
Priority: Blocker
Priority: High
....
Yes, unfortunately this feature is not intended to exclusively select one value per category as these are labels.
There is a github issue that proposes a new feature to GitHub so that we can have a Priority attribute in every GitHub issue right here
https://github.com/isaacs/github/issues/472
Not sure about all the other custom attributes, but maybe this would be a good start for your idea.
There does not seem to be a way to create custom parameters. You may be able to do this by storing the data inline in the text of the issue and then parsing that issue text programatically, but that's kind of a hack.
For instance, if you wanted to link a GitHub issue to an internal bug tracker like JIRA, just use the JIRA issue name in the text of the GitHub issue and then write a regular expression to parse it back out. This requires a little bit of extra plumbing on top of GitHub.
Date opened and closed are available in the API. See documentation.
(Incidentally, I'd note that the lack of customisation and complexity is a key feature of GitHub's issue tracking system: it is designed for developers, not project managers who want to tweak it into a confusing JIRA-like hellscape of misery.)
Update June 2021: you could use custom fields for those attributes!
New beta features within GitHub Issues, with better ways to plan, track, and manage projects.
Read more on the GitHub Issues page or in the FAQ.
✨ NEW – Project planning for developers
Available in limited public beta
Built like a spreadsheet, project tables give you a live canvas to filter, sort, and group issues and pull requests.
Tailor them to your needs with custom fields and saved views.
Sign up for the beta now.
That includes:
Extend issues with custom fields with support for text, number, date and single-select types
Change custom field values right from the issues sidebar
Filter, sort, and group by any field
Use tags
Most of the time you can put the kinds of things you want in the body of the issue as text or use a tag for things like priority. You only need to set priority if it's not the default one.
TRAC tends to separate wiki pages and tickets quite a lot, but there is definitely an argument for cross-reference.
I know that the TagsPlugin unifies both ticket "Keywords" and a new "Tag" list for wiki pages. I'm looking for a similar functionality for components and milestones. Is it possible with TRAC 0.11? If not, what about more recent versions?
Do I understand correctly, that you request/vote for tagging Trac resources milestone and component? This is reasonable, and could be done, because TagsPlugin is ready for tagging arbitrary Trac realms just by implementing the ITagProvider interface, i.e. by subclassing DefaultTagProvider, and you're up and running with the generic tag store in Trac db table tags as tag store.
Or is your request more about functionality like that provided by
ComponentsProcessorMacro - listing project components with descriptions
ListMilestonesMacro - shows a list of chosen Milestones
MilestoneCompactMacro - milestones displayed in compact table or list
MilestoneQueryMacro - displays a list of matching milestones
PlannedMilestonesMacro - lists milestones ordered by their due dates