Is there a way to mark issues with different options than the default Bug\Feature\Support options in Redmine under the "Tracker" field?
Of course, you may define your own trackers in redmine: Administration -> Trackers lists all existing trackers and lets you add new ones.
Related
When I open a ticket I see a list of prior interactions.
I would like that list to also include the time spent/reported when the interaction was added.
But how? There are soooo many configuration options!
Regards,
Jeroen Baten
if by list of prior interactions you mean the article list, then I'm afraid that you can't do that just by config options. You'd need to edit the module and the template.
if not, please add an screenshot or some explanations of what you want and where you want it.
I am evaluating Redmine, and I wonder if there is any advantage to Categories over Custom Fields?
Indeed, Categories can't be shared between projects so far and it's a strong drawback for me.
I have the feelings categories are only useful if one needs different categories between projects.
In other words, it's a project property instead of a tracker property like custom fields.
I am missing something here?
Thanks you!
In Redmine, Category is a standard field used by trackers and has different values defined for each project in the project 'configuration' tab.
Category values cannot be shared nor inherited in Redmine projects.
This is some serious drawback which is discussed by the community. A patch is available to customize Redmine, but it targets an old version of the application.
An alternate solution is to create a custom field, say Cat, which would be used as a category. That Cat field can be used by any project with any tracker.
It also means that the Cat values are shared for all projects which can be pointless if you have a 'cooking' and a 'mechanics' projects...
There are two solutions to deal with it :
Create a Cat custom field for each project, but the name of the custom field has to be unique
Use the Custom Values Per Project plugin to limit available Cat values for each project, which can be a pain i you have lots of projects
You can even possibly use a combination of those two !
That is the only solution I have found so far.
I am building a brand new website in Sitecore and I am looking for advice on the following scenario:
My site has 2 version of its homepage. Both are quite different. The layout is the same, but most of the components and sublayouts on it will change depending on whether the user is logged in or not.
Does anybody has a suggestion of a good practice, or way to do that in Sitecore? My basic requirements are, have a single URL for both (the website root, it is a homepage) and do not harm the content author experience.
My thought so far was:
Use of personalization to control the components to be displayed (Concerns: performance and the content author experience he woudnt have to change component by component to see both versions)
Use of two item in the tree and intercept a pipeline to resolve the right item at the right time (Concerns: the content author would have two home items to maintain *not actually a big problem)
Does anybody has any other approach or considerations on those I listed?
Thanks
An alternative solution would be to make use of devices, and use a pipeline to switch devices if the user is logged in.
Set up your Device in Sitecore to use the default layout as a fallback so it does not affect other pages in your site (and they continue to work as expected). You are then able to set different sublayouts and components for that Item (directly or in Standard Values for the template) for each device. You can make use the VaryByDevice caching option to make better use of the Cache.
Your content editors can also switch between the devices easily in the Page Editor from the ribbon. Any further customization you need in other areas of the site, such has switching out a single component, can be run using a Personlization Rule taking advantage of "where the current device compares to value".
It does sound like you have the need for personalization based on authenticated status, so I would recommend staying with the built-in personalization interface to avoid confusion. Authors will have been trained during Sitecore training on how to use personalization, and introducing an alternative method for accomplishing the same thing could lead to a less-than-optimal experience for the author.
To address your concern of the author needing to view components by toggling each one, I would recommend installing the Experience Explorer module. You can create presets that meet your rules on your presentation and then the author can preview the site for different 'experiences'.
If you have a single URL for the home page, it is more straight-forward to go with a single item, so I would definitely advise against having two home page items that are being resolved by the same URL.
You mentioned a concern for performance, so I would recommend you making sure that you enable your sublayout caching settings. In your case, varying by Data may be the way to go, given you would personalize with two sets of datasources.
In the past I have used the following crude technique:
Make two components, one for "logged in" and the other for anonymous.
Each rendering has just one line, a single placeholder, either:
<sc:placeholder key="logged-in" runat="server" />
or
<sc:placeholder key="anonymous" runat="server" />
For "logged in" I make a personalisation rule which hides the component if anonymous, and for the anonymous component I make a personalisation rule which hides the component if the user is logged in.
I then nest all the components under the correct placeholder key.
I am using DataGrid for displaying table. One of the columns in Datagrid consists of XamFormulaEditor. Also, there are some custom variables that are assigned to XamCalculationManager's Named references so that they are visible to user when he types formula in XamFormulaEditor. I have couple of problems with ContextualHelp:
For Eg. if the custom variable name is "a", then in ContextualHelp list it looks like [//a]. Isnt't there any settings to make it look like [a] ?
Is there any way to filter the contextual help to not display standard functions and only display variables that we want ?
After looking into this and doing some research, ContextualHelp on Infragistics XamFormulaEditor for custom variables has been determined to be a new product idea. You can suggest new product ideas for future versions (or vote for existing ones) at Infragistics new site for features:
http://ideas.infragistics.com.
There are many benefits to submitting an product idea:
- Direct communication with our product management team regarding your product idea.
- Notifications whenever new information regarding your idea becomes available.
- Ability to vote on your favorite product ideas to let us know which ones are the most important to you. You will have ten votes for this and can change which ideas you are voting for at any time.
- Allow you to shape the future of our products by requesting new controls and products altogether.
- You and other developers can discuss existing product ideas with members of our Product Management team.
Steps to create your idea:
Log into the Infragistics Product Idea site at http://ideas.infragistics.com (creating a new login if needed).
Navigate to the product / platform channel of your choice (e.g. WPF, Windows Forms, ASP.NET, HTML5 / Ignite UI, iOS / NucliOS, etc.)
Add your product idea and be sure to be specific and provide as much detail as possible. Explain the context in which a feature would be used, why it is needed, why it can’t be accomplished today, and who would benefit from it. You can even add screenshots to build a stronger case. Remember that for your suggestion to be successful, you need other members of the community to vote for it. Be convincing!
The Product Idea site puts you in the driver’s seat and allows you to track the progress of your ideas at any time, see how many votes it got, read comments from other developers in the community, and see if someone from the product team has additional questions for you.
Is it possible to apply security restrictions on older version of items?
I would like to restrict read access to previous versions of item for particular roles.
You cannot set security on specific versions.
If you change it for one version of an item, it will be changed for all versions of that item.
I wonder in which case this could be useful though.
The security field is 'shared' across versions, meaning it's value it always the same across all versions of the item.
This is one of Sitecore's default fields, so I'd suggest not to change it.
However if you really want to, you can go to /sitecore/templates/System/Templates/Sections/Security and untick the box on the right called 'Shared' for the field '__Security'.
Then you can go to each item and manually change the security settings for each version.
Disclaimer: I have no idea what effect this could have on security applications, so I don't know if the security editor would stop working, or if Sitecore in general would start to slow. Either way, I would advise against doing this, as I'm not sure it's recommended.