Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
Is there any Jira Plugin for Subversive that let's you choose the Jira Issue in the Subversive commit Dialog?
Backgound:
For now we write the Issue Number manually in each commit.
Problems:
accidentally committing to the wrong Issue because Number was mixed up
needs more time to switch from Jira to copy the number to Comit Dialog and paste it
atlassian connector for eclipse provides a way to import JIRA data into eclipse. Not sure if it lists the issues on commit screen. However, you won't have to switch windows at least.
Two other possibilities are:
a) the JIRA Commit Acceptance Plugin
https://plugins.atlassian.com/plugin/details/289
It allows to check if the issue does exists in JIRA and optionally if the committer has been assigned the issue.
b) TortoiseSVN Plugin
Allows to list issues (using a JIRA filter) and indicate for which issue the commit is being done
https://plugins.atlassian.com/plugin/details/10017
Although I strongly believe that the commit-to-issue linking should be handled in the server-side (not by trusting the SVN client), the JIRA Commit Acceptance Plugin mentioned in Francis' answer is not maintained for several years.
Earlier this year we analyzed its shortcomings, and built a new JIRA add-on to tackle the same problem using all modern JIRA features, like:
JQL for super-flexible conditions
P2 framework for fast installations and upgrades without JIRA restarts
Standard REST API
(The full comparison is available here.)
The new add-on called Commit Policy is available from the Atlassian Marketplace!
(Diclr: I'm a developer working on both the old and the new add-ons.)
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
We are using JIRA Software and JIRA Service Desks in our company.
I am new to JIRA and i want to ask if it is possible to create a test environment for a few projects or service desks? If yes, how can i set it up ?
Mfg
Technically, JIRA ServiceDesk is a Plugin in JIRA and it uses AO Tables. With that said, JIRA Project Export and Import doesn't support Exporting AO Tables. It means that you are not able to import ServiceDesk Projects to the other instances. You can take a look at their feature request here.
Thus, I would say it's better to clone the full production instance into a test environment. In order to do that, you have to create backup from home directory, installation directory and database and restore them into a test instance. Full steps are available here in Atlassian Documentations.
Please note that, prior to start the staging environment you have to disable incoming and outgoing emails with the available JVM Arguments. Otherwise, new issues will create in your test servers instead of production.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
In one of my projects we are using Jira and Greenhopper (with Confluence) to manage everything related to the project.
Another client I'm about to start working with uses TFS with workitems and the lots. After reading some material about TFS and its "agile setup" (and seeing some demos), I am wondering if I can get the best from both worlds. TFS can still host the code and the work items, but something else gives me the planning board, task board, burndown reports, etc.
I've googled a little and found products like this: http://www.targetprocess.com/ and http://www.eylean.com/.
Does anyone know about them and can comment on them, or comment on other similar tools?
I am a sales manager of Eylean Board and ,as you mentioned, it has an integration with TFS. One of the main features that lets you easily use both tools is that Eylean simply visualises TFS work items on a Kanban board, so you wont need to learn a new tool. Other features include a time tracking system, various reports, drag and drop for task assigning, additional information for each task, etc.
More information can be found here: http://www.eylean.com/tfs
Even though this is officially off-topic (tools related advice is off-topic for StackOverflow):
Not that I know of, there are tools though that extend Team Foundation Server with additional features:
Urban Turtle,
VSO Enhancer
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am about to start using Visual Studio 2012 Pro with Azure Websites. I am not using Source control at present. However the idea of rolling back previous versions is very appealing if new code does not work. I really want to keep this as simple as possible.
The options I see are:
1.) TFS (service)
2.) GIT from Local repository to Azure Repository.
3.) Hosted GIT. SInce I am not using GIT at present, then I think this could become an unnecessary extra step.
I am using MVC3, EF4.1, SQL Server, C#.
From your experiences of both, it would be very interesting to hear of your observations
Thank you in advance.
EDIT:
Yes it could be opinion based, but I was hoping for some factual feedback from any folks that had perhaps tried both. I have altered my question above accordingly.
You can use Visual Studio Online. It integrates well with Azure Management Portal and offers both TFS and Git.
Visual Studio Online is free for up to 5 users. Whether you want to go with Git or TFS, I suggest you play around with both and then decide which one you like.
It also offers Agile and Scrum development process templates.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
In JIRA we have set up several projects for the same software tool - one for each customer since we have to adapt the software very often to the specific requirements of the customers. So bugs, issues and feature requests in JIRA end up in different JIRA projects. When a major update of our software tool is released to all customers, we are facing the problem to create release notes containing all JIRA issues cross the various JIRA projects which have been solved e.g. in version 2.3.0.0 of the software or higher.
The standard JIRA functionality makes it very easy to create release notes within one JIRA project for a specific version, but what we need is a filter across various projects for various version numbers. Since the version field in JIRA is a text field and not a number, a query for version number > 2.3.0.0 does not work.
Has anybody an idea how to solve this problem?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 2 years ago.
Improve this question
I am liking JIRA a lot, but we need a CLIENT/PROJECT/ISSUE Schema. Not Just Project and issue. It seems that Projects in JIRA are actually Clients. If you have many clients each with its own projects and issues it seems silly that you cant manage clients. It does so many other things so well, it seems strange.
Some companies indeed use JIRA Project as clients, and use JIRA Components (which are parts of a project) as the projects.
Note that permissions, issue types and other configuration "schemes" in JIRA are configured per-project, not per-component. That means that with this schema you will be able to set up permissions for all issues belonging to a specific client.
Versions are also set per JIRA Project, i.e. per client in this case, which also might not be good.
JIRA also has Project Categories. If you have a small number of clients, you might do better with assigning a client to a project category, and then project will be JIRA project.