Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.
Project Management
3K
Solutions
6K
Contributors
Project management is the discipline of carefully projecting or planning, organizing, motivating and controlling resources to achieve specific goals and meet specific success criteria. A project is a temporary endeavor designed to produce a unique product, service or result with a defined beginning and end (usually time-constrained, and often constrained by funding or deliverables) undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value.
Share tech news, updates, or what's on your mind.
JIRA: Removing old sprints from migrated ticket to resolve a velocity chart issue
Ran into an interesting problem in JIRA that I managed to solve this morning. Figured it might help out others, so here goes!
It turns out that if you had a ticket that was part of a Sprint in one Project, but then either move it to another project or clone it, it'll still retain a history of the prior closed sprints it was in. At first, that doesn't seem like a big deal, but it means that the Project it's now part of will have messed up Velocity Charts, because it'll start including the Sprints from the other Project. And there's no obvious way to remove the old Sprints from the ticket (editing the ticket only lets you change the current Sprint assignment, not clear out prior ones.) No good!
Fortunately, the Bulk Edit feature provides a workaround and will let you clear out the old Sprint associations, which will then fix the Velocity Charts. And here's how to do it:
For reference:
Ran into an interesting problem in JIRA that I managed to solve this morning. Figured it might help out others, so here goes!
It turns out that if you had a ticket that was part of a Sprint in one Project, but then either move it to another project or clone it, it'll still retain a history of the prior closed sprints it was in. At first, that doesn't seem like a big deal, but it means that the Project it's now part of will have messed up Velocity Charts, because it'll start including the Sprints from the other Project. And there's no obvious way to remove the old Sprints from the ticket (editing the ticket only lets you change the current Sprint assignment, not clear out prior ones.) No good!
Fortunately, the Bulk Edit feature provides a workaround and will let you clear out the old Sprint associations, which will then fix the Velocity Charts. And here's how to do it:
- Run a search that'll return the ticket you need to remove the sprints from.
- Choose the "Bulk Change" option from the "three-dot menu" in the upper right.
- Check only the ticket you want to change. Hit Next button.
- Choose "Edit Issues". Hit Next button.
- Check the "Change Sprint" option. Leave it blank. Hit Next button.
- Review the Confirmation screen. Hit Confirm button.
- Hit Acknowledge button when the progress meter is done.
For reference:
Active today
One word of caution: be careful when doing this! Bulk Change is quite powerful and if you're not watching out, you could accidentally change a lot more than what you really want to. I imagine this is why Bulk Change has so many steps to it... Sometimes I'm glad when a task is a bit difficult and cumbersome to do :-)
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE
Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.
I'm not a SharePoint expert by any means, but I've loosely followed the a guide online (sharegate) for creating a Project Management site, where you have sub-sites as "projects" created from a site "template" to keep uniform, consistent sites with apps/web parts to manage a project.
I then have a content query on the main site that shows all the sub-sites, which are effectively all projects.
Problem I'm having is determining how to know when a project is "complete" and thus how to then remove it from the content query at the top. No sense in having projects showing up if they were from years ago.
I also would rather not delete them, for historical purposes and reference (could be some good useful documents in their doc libraries for example).
So with existing 15 projects, anything I can do to each site like add a drop-down or form where the project is marked active/complete, etc, and then modify a the search query to exclude them?
To give the same example from the article I followed, the query is like this:
path:"http://demo/projects" contentclass:STS_WEB Site<>{Site.URL}
I then have a content query on the main site that shows all the sub-sites, which are effectively all projects.
Problem I'm having is determining how to know when a project is "complete" and thus how to then remove it from the content query at the top. No sense in having projects showing up if they were from years ago.
I also would rather not delete them, for historical purposes and reference (could be some good useful documents in their doc libraries for example).
So with existing 15 projects, anything I can do to each site like add a drop-down or form where the project is marked active/complete, etc, and then modify a the search query to exclude them?
To give the same example from the article I followed, the query is like this:
path:"http://demo/projects" contentclass:STS_WEB Site<>{Site.URL}
Successful collaboration among team members is essential for the growth of your business. When employees work together on projects, share ideas and communicate effectively they get better results.
Free Tool: Site Down Detector
Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
Project Management
3K
Solutions
6K
Contributors
Project management is the discipline of carefully projecting or planning, organizing, motivating and controlling resources to achieve specific goals and meet specific success criteria. A project is a temporary endeavor designed to produce a unique product, service or result with a defined beginning and end (usually time-constrained, and often constrained by funding or deliverables) undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value.
Top Experts In
Project Management
-
1
xtermie2,400 points -
2
gr8gonzo2,120 points -
3
Colleen Kayter2,000 points -
4
Oscar Waterworth246 points -
5
Ritesh Ratna71 points -
6
Jessica Riga68 points -
7
Sina May40 points -
8
Experts Exchange38 points -
9
Kevin Cross33 points -
10
Sandeep P R31 points -
11
Shakshi Shivi29 points -
12
Lisa Michaels29 points -
13
Mark Bullock26 points -
14
Ryan Kilimnik23 points -
15
Dan Radak21 points -
16
Mark Wills20 points -
17
Abbas Haider Ali18 points -
18
TRTurner12 points -
19
jjperezaguinaga10 points -
20
Eric AKA Netminder9 points -
21
GreyCampus Inc.9 points -
22
madhubk8 points -
23
jusgre444 points