In other project types it was possible to insert link into ticket, and status was shown like here:
But I can not do it with Kanban, why?
As per Atlassian Confluence, the project administrator must set the jira.projectkey.pattern property to the proper regex expression.
The default regex is ([A-Z][A-Z]+).
Related
I have several dashboards in JIRA and want to create a central one where there is a filter or gadget that will display links to the other dashboards. Is this possible?
You may save all of these dashboards' URLs and show them inside a gadget in your main dashboard.
Let's say one of your "other dashboard"s link is: your-jira-url.com/secure/Dashboard.jspa?selectPageId=10000
Then, you can add a new gadget (like Text plugin which can show HTML) and add following HTML in that gadget:
Link to the other dashboard
However, Text plugin is not enabled default because of the security issues. You may find the details on Atlassian documentation.
Also, as an alternative, you may try HTML for Jira plugin, or you may find some free alternatives from Marketplace.
I found a way to accomplish this. You can embed it in a issue ie the description field and use a filter to display that field of that issue
Is there a way in TFS that user have permission to add Issue in a project and should not have permission to add/edit other work Items like User Story etc ??
is there any extension or utility to do this on TFS ??
You cannot restrict the editing of specific work item types. Permissions are controlled at the area path level. A user with permissions to create work items under an area path can create any type of work item under that area path.
No, there is no such build-in configuration. It's also not able to use any extension or utility to do this on TFS.
Permissions for work items are based on the areas/iterations where they occur, and are set through the dialogue that defines areas and iterations.
In other words, you are not able to set any permission either to a specific work item or work item type.
You could submit a user voice here, our PM will kindly review your suggestion.
There is only one out-of-box way to do this: Create child nodes, modify work items under an area path. You may try the following:
Create new team and area path for Issues Team Add a team, move from one default team to several teams.
Edit Security for the Root Area Path and restrict edit work items for the Issues Team.
Edit Security for the Issues Team Area Path and allow to edit work items for the Issues Team.
In this case, your Issues Team can create and edit any work items under Issues Team Area Path, but can not edit any other work items.
Need to add a new item is drop down in Jira. Did not found, searched for long time.
It's probably a custom field. Jira admins can change them
Unless this field comes from a plugin (Jira Server) or addon (Jira Cloud) it is a custom field. You will need admin permissions to configure a field. To add another option navigate to "Custom Fields" page, locate "Platform" field and choose a cog icon > Configure then click the Options or Edit Options link and you will be able to add new options there. Not sure which Jira version you are using, here you have a documentation for this for Jira 7.1.
In my implementation of JIRA, I have a custom field called Developer which gets populated automatically (username) whenever someone move the JIRA from Open to Fixed state. Now I want something similar for the Fixed to Reopen transition. That is, whenever the tester changes the status to Reopen, it should go back to the Developer or the Project Lead (in case the field isnt populated as the custom field can be overridden).
I tried to implement a post function, but there isn't a way where I can use OR criteria. Or is there a way?
You can do a Post Function on the transition using the Script Runner plugin if its a self-hosted JIRA instance which will allow you great flexibility in the logic to fill the target field in.
I finally managed to find a workaround for this.
Download the Workflow Enhancer for JIRA plugin (FREE). You would also need JIRA Suite Utilities (I had it installed already for some other customization)
In the Fixed to Reopen transition, add a Post Function and use Copy Value From Other Field to update Assignee from Developer field
Then add another Post Function underneath this where you need to use Universal Post Function. Here make the boolean condition as {Assignee}=="" and select Choose post function to execute: as Assign to Lead Developer
Publish the draft.
I am attempting to add a "Requested By" field to a custom Work Item Template in TFS 2010. When I create the field in the work item, I wish to have the values restricted to a particular AD group. I'm looking for functionality similar to the "Assigned To" field in the standard templates. However, if I add this AD group to one of the TFS groups, they all get added as valid users in TFS and that is not the behavior I'm looking for. I simply wish to restrict the values for a field to an specific AD group. I've tried adding the AD group to the "Group" property of the VALIDUSER field definition rule, but I get the following error:
---------------------------
Error
---------------------------
Error importing work item type definition:
TF26204: The account you entered is not recognized. Contact your Team Foundation Server administrator to add your account.
---------------------------
OK
---------------------------
Thanks in advance!
[Update]
On further investigation, I have found that it works with certain AD groups, but not with others. For instance, it works with our "Developers Group" but not with "Domain Users". It's actually a fairly small subset of groups that I've tested that work. Again, Any help would be appreciated!
The simplest way I've found is to use the ALLOWEDVALUES field definition rule. Add to the list of allowed values the name of a TFS Group. I have still not been able to get the AD group to work directly. But my big problem was that when I was trying to use a project group, I was putting the project name in the "[Project]\Group Name".
As stated here
some people may think that “[project]” is a place holder for the
project's name, but it is meant as a literal.
You should be able to add an AD group, by simply writing it as domain\group.
Note, however, that the group needs to have some access privileges to the team project (e.g. A member of Contributers).
Have you tried to create a TFS Group, add the AD group in the TFS Group, then add the TFS Group in the "Group" property of the VALIDUSER field definition ?
If I remember correctly you can't put AD group in the "Group" property of a TFS Field, but only TFS Groups...