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.
Related
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 4 years ago.
Improve this question
I plan to use JIRA-Agile as used to:
EPIC->US->Task
Nevertheless, the JIRA is not only used by one project but rather by a couple of projects, which cooperate or even interfere in a few topics.
At the end I want to mark up which EPIC belongs to which project. I thought about to use labels or components, but for me it seems not very suitable. What is the best (may even standard) way representing this project structure above the EPIC level ?
Features I need:
Epic can belong to more than one Project
Epic can be shifted between projects
Projects existing on different levels (one Project can even combine 2 smaller one)
"nearly" automatic reporting export is possible
Project structure can be "read" from the Jira
Are you asking about project management and analysis in jira.?
if so then you can see if the Jira Portfolio management app works for you
https://www.atlassian.com/blog/jira-service-desk/portfolio-for-jira-2-0-is-here
I am not sure how Epic will help in your case -- lets hear more answers here.
Well i am not sure if a jql will make it happen, but https://softwareplant.com/jira-aggregate-multiple-sprints-single-screen/ could help you.!
it has an option to view the board based on Epic, userstory also.!
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 5 years ago.
Improve this question
I need to provide some metrics on my Scrum team for management. The most important metric is how many story points are assigned to each member during a sprint. I would like to just assign them to the team in general, as that would be a better implementation of SCRUM, but unfortunately I can't do that.
Anyway, I have been looking for a dashboard gadget that will track how many points are assigned to each team member, how many story points are verified complete, and how many remain. So far the search (in Jira documentation, google, and stackoverflow) has yielded nothing. My current solution is to put all of the information in an excel spreadsheet. This works, but seeing how all other metrics are integrated into a Jira gadget or the like, I would really like this to be present on my board.
So again: Can I use JIRA gadgets to track story points per developer?
*Sorry if this is not the right community for this question, but searching JIRA in stackexchange brought me here.
Credit to https://answers.atlassian.com/questions/9383627/i-need-to-see-the-total-story-points-per-user-in-the-sprint- for the answer
If you look at your sprints in plan mode, you see the people that are assigned work in that sprint just below the sprint start and end date. To the right of the people, you see 3 dots, which when clicked will open a summary showing every assignee and the number of issues and associated story points assigned to them.
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 8 years ago.
Improve this question
I need to find an easy way to maintain a set of different iOS apps but that they will be very similar one to another. Too similar actually, the differences will be just regarding the content.
Following the typical way of releasing/updating an app, it would imply:
Create a "core project" of the app with all the functionality and UI.
Create n projects that reuses the core project. Every project would just provide a DB with different content.
Having to release/update every single project/app to the AppStore
This would be too time consuming. Is there a tool or a methodology that can help us speed up the process and help the maintenance?
The built in process for this is to create multiple targets in a single project. Each target will have its own info plist, etc.
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.
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.)