PROBLEM: There are two Jira projects: A & B. When project A transitions, project B should as well. Issues from projects A & B are linked.
RESEARCH: There is an ILA plugin for Jira and in its Update Status Transition you can select issues with JQL and set their statuses.
I've conducted a JQL, but it is related to current issue, and I need it is a variable which is unavailable (find issues of project A, linked to issue B-3 from project B):
project = "A" AND issue IN LinkedIssuesByJQL("issue = B-3")
QUESTION: How to refer to a variable like $currentIssue? Any other free plugins? Maybe using Jira API?
I don't know the ILA plugin for Jira but it seems that it does not provide the functionality you require. You might want to reach out to them and ask if they can implement this feature for you. But based on their documentation, it's a rather simple plugin for smaller use cases.
However, your use case also sounds you might want to use some more automation than this. Here are three alternatives you might want to consider for your problem:
Jira Service Desk Automation
In case one of your projects is a Jira Service Desk project on Jira Cloud, then you could use Jira Service Desk Automations which is a free feature. It allows to define rules and actions to be performed. You can find more information here.
Automation Plugins
There are a few other plugins (or 'apps') available on the Atlassian marketplace to automate certain tasks in your projects. They work similar to the Jira Service Desk Automation but are much more powerful and can be used in more than only Jira Service Desk (of course they support regular Jira projects). Your use case should be possible with them as well. Popular apps are Automation for Jira (there is a lite/free version available) or ScriptRunner (here you have to write your own scripts).
Issue Synchronization Plugins
There are also specialized plugins in case you want to continuously make sure that the issues in your two projects have the same data and the issue updates are synchronized to the other side as soon someone updates an issue. They not only provide you with settings for workflow updates but also regular issue field updates. Popular ones are Exalate Jira Issue Sync or Backbone Issue Sync, but none of them is free to use. (Note: I'm currently working for the team behind Backbone Issue Sync).
Although neither of the unswers suggest free plugins as requested, I also had some helpful comments in Atlassian Community:
Sync fields is a plugin which is used to change and replicate all the data that is in a issue to another issue in other project ,may be this is similar plugin.
There are many options out there to do linked transitions:
Jira Misc Workflow Extensions has a transition linked issues post function
JSU Automation Suite for Jira Workflows also has one
You can also (partial list)
Automation for Jira, (this one was recently purchased by Atlassian)
one of the scripting addons (scriptrunner, power scripts)
Jira Workflow Toolbox
So there are many options. Take a look at each of the addons and see which one has the most features that you would use in addition to linked transitions. They are all good choices, and all have their pros and cons.
Related
I am looking for advice.
I have a requirement to generate 5 PBIs under a Feature. We need the user to be able to trigger the process by populating a field for example.
Do I need code for this or is there a codeless method?
I can see that I can build Plugins for TFS. I saw an example or two (although they were related to code check-ins). I would be looking to investigate a trigger around the save of a feature and if a specific thing has occurred generate some child PBIs.
Ideally I would like a codeless method within TFS for this but am happy with investigating a Plugin if necessary.
We are on premise now but may move to online in six months or more.
If you`ll move to online, you have several options and they are not codeless:
Use existing solutions, example: TFS Aggregator
Create a custom web service to listen events and do some actions: Web Hooks
Create a custom application and use it as scheduled task: Automation of state changing for Azure DevOps work items
In our work place we use Team foundation server as the main server used for source control, work tracking, build server etc.
We develop in house software with many teams working on different projects.
Sometimes we develop applications or libraries which can and should be shared in our company including the ability to have more than one team contributing. Unfortunately due to nature of the applications being developed they cannot be shared outside our company.
I would like to know if tfs can help in that respect or do I need to add other tools.
For instance if our teams work in different areas or team projects how can open source projects be shared without risking editing permissions or such. How can projects be shared, cataloged, published?
How can issues be published for the project? How can pull request be done as they are done in github?
Share projects or source code in TFS is accomplished mostly through a combination of using the Area hierarchy and Teams functionality.
Then we can use the Area field to filter all reports and queries. Each Team is tied to the related Area and is used to provide each Team/Sub-Project with it’s own Product Backlog. And Security can be granted based on Area and/or Source Control Path.
Update
Permission is a very important concept in TFS. The simplest and safe way is using permission to restrict and help other team contributing to the share projects. One main team/group which have all permissions for the contributing to the share project.
Most of the teams/groups which have visibility into the share projects. They need to create pull requests to review and merge code in project. Pull requests let your team give feedback on changes in feature branches before merging the code into the master branch. Reviewers can step through the proposed changes, leave comments, and vote to approve or reject the code. The same thing as GitHub.
And many times a request or issue fix will come from the share project managers , but they are not sure what team or project it should be assigned to. Then you could use share product backlog items (pbi, or user story if you are using agile template) across team projects within TFS. Since you are using a multiple team strategy under a single team project. You could collect the pbi’s and place them in an oversight queue that will be reviewed by either an individual or committee. Then these pbi’s will get moved as they get assigned to teams and projects. However, you also need to setup security in way so that the individual teams don’t have permissions to get in and monkey around with other teams backlog, queries, or code.
Otherwise, there are no built-in share project process or tool inside TFS, if you really need this, could add a uservoice.
I am using JIRA from a pretty long time and its good, but now I want to store all the project document in a single place like sharepoint (with version if possible).
Do I need to create a ticket and then attach to it?
OR
Is there any separate place for it in JIRA?
I believe you should try using Confluence, which is itself part of the Atlassian stack of software development/productivity tools. Confluence is a feature-rich document/knowledge sharing application which is somewhat comparable to SharePoint and offers great integration with Jira and its other sibling products).
I'm looking for a tool to track questions and answers between the development team. After then I want to compare the employees based on their activities via some reports. Currently we're using MSF for CMMI 4.2.
Is there any process template to support this situation? For example having work item types like Question, Answer, Article.
Is using TFS a proper tool for this purpose?
Or maybe there's some better tools available which I'm not aware about.
Is there something like StackOverflow which I can use locally in the company?
You can upgrade tfs to tfs 2013 which supports team rooms where your team members can chat which also can be used as q&a tool. You can try this now in tfs service.
http://tfs.visualstudio.com/en-us/learn/collaborate-in-a-team-room.aspx
You can also set up your own company wiki website where your team members can update q&a.
What is the best ASP.NET WIKI out there?
Or set up your own in house stackoverflow
https://meta.stackexchange.com/questions/2267/stack-overflow-clones
It sounds like you want a discussion forum. If you are using SharePoint (e.g. for the TFS Project Portal) you can create a discussion forum in SharePoint.
In TFS Work Items there is also the ability to track a discrete list of comments/discussion under the History tab.
you can also integrate them with Microsoft Project Server Or Microsoft Dynamics CRM.
there are many tools there , waiting for you , to solve your other problem.
http://www.quantumwhisper.com/dynamics-crm-microsoft-tfs-integration/
crm has many feature for that
http://intovsts.net/2012/12/28/integration-of-dynamics-crm-2011-solutions-with-tfs/
in the project server also exist many lists like issue tracker, or risk for send messages interactive between your team and others.
We would like to give our customers access to report bugs and to look at existing bugs and work items, through Team Foundation Server.
For that, we will need a web frontend, which is customer-friendly. It should be easy to use and with a nice UI. I am aware of Web Access, but think it is too developer-oriented for our customers to use.
Is there any good open source or commercial products out there for doing this? It is important that we will be able to customize the products for our needs.
There is WIWA, but it's quite similar to the regular web access tool. It exists more as a licensing aid (helping TFS admins ensure they don't overstep the CAL requirements) than as a fresh new UI aimed at non-developers.
Note: get it from the latest download package for TSWA SP1, not the CTP linked in the blog post
I don't know of any other solutions that are as customizable as you're hoping. I've seen (and contributed to) one-off solutions that were tailored for a specific work item type. At the broadest level, you could say that the bug pages # connect.microsoft.com and # Codeplex fall into that category as well. But none of them is publicly available, nor would they be helpful even if published.
You'll probably need to do a one-off of your own using the Work Item Tracking API. Luckily, this is far easier than writing a generalized workflow engine / forms designer that knows how to parse WIT XML.
A bit of a shameless plug as I'm the project owner: Spruce is an ASP.NET MVC2/jQuery driven front end for TFS 2010 aimed at replicating the user-friendly approach you find in products such as Fogbugz, Unfuddle and online sites such as Github, Bitbucket.
A few screenshots:
I'll be adding the list of features found on the blog at the start of the year.