The real issue with jira is how unresponsive the backend feels.
I used it (Jira) for a short period of time a while back. I seem to recall that it's performance was highly influenced by non-obvious JVM parameters, and bits of the system would stall or crash without a clear pattern until a bit of trial & error with parameters solved it. It wasn't very "turn key" and the out-of-the-box config were... less than ideal. This was for a single user (me) so it's not like there was a much…
A Simplified Jira Clone Built with React/Babel and Node/TypeScript
61–70 of 101 posts
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#62Earlier quoted context omitted.
What do you prefer to Jira? At a former workplace we used Gitlab, which was a pleasant suite to use. These days we use Atlassian and often find myself incredibly frustrated by their products
Request Tracker (RT) is awesome. Does it look good? Nah, not particularly.
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#63maybe dont call it jira_clone. People dont like installing something called a "clone". Brand it differently and build something really cool here
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#64Earlier quoted context omitted.
I used it (Jira) for a short period of time a while back. I seem to recall that it's performance was highly influenced by non-obvious JVM parameters, and bits of the system would stall or crash without a clear pattern until a bit of trial & error with parameters solved it. It wasn't very "turn key" and the out-of-the-box config were... less than ideal. This was for a single user (me) so it's not like there was a much…
Most pages take 10+ seconds to load for us and we are using Atlassian's hosting.
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#65Creator of "Jira Clone" here. First of all I want to make it clear that this is just a showcase/demo product. It's definitely not something I'm planning to sell. Additionally, it's not even remotely production ready, and it's missing about a zillion features that would make it a full-fledged project management software. The main reason I built this was to have a good showcase for potential future clients. The second…
Fewer features sounds great. I personally loath Jira, and avoid using it whenever possible, but your clone looks really nice. You can improve 100x on Jira just by making it faster, simpler, and easier to use. One suggestion: it looks too similar to Jira, you might want to change the design a bit so that Atlassian doesn't try to sue you or something.
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#66Just randomly reading into React over this example, I'm surprised by how React itself confused me with the useState function.
let _count = 0;
function Component() {
return (
{_count}
{ _count++; render(); }}>Increase
);
}
function render() {
React.render(, root)
}
Or you can abstract it: let _count;
function useCount(initialValue) {
return [_count, (value) => { _count = value; render(); }]
}
function Component() {
const [count, setCount] = useCount(0);
return (
{count}
setCount(count + 1)}>Increase
);
}
And then generalize it and make each state dependent on the order of useState calls: const states = [];
function useState(initialValue) {
const state = states.shift() || { value: initialValue }; // Pop or create
setTimeout(() => states.push(state), 0); // Defer the push
return [state.value, (value) => { state.value = value; render(); }];
}
function Component() {
const [count, setCount] = useState(0);
const [name, setName] = useState('World');
return (
{count}
setCount(count + 1)}>Increase
Hello {name}
setName(e.currentTarget.value)} />
);
}
Actual hooks also track the component that's being rendered, and don't just call the global render function, but that's pretty much the whole useState implementation.Here's a codepen: https://codepen.io/lxe/pen/RwbXPKo
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#67Earlier quoted context omitted.
I would much rather not deal with jira tbh. Some companies take it too far and use jira as a micromanagement tool.
I’ve found jira dysfunction often reflects the dysfunction of the underlying corporate structure.
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#68Just randomly reading into React over this example, I'm surprised by how React itself confused me with the useState function.
useState is a memoization technique and an abstraction to hide global state. You can do: let _count = 0; function Component() { return ( {_count} { _count++; render(); }}>Increase ); } function render() { React.render( , root) } Or you can abstract it: let _count; function useCount(initialValue) { return [_count, (value) => { _count = value; render(); }] } function Component() { const [count, setCount] = useCount(0);…
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#69However; if you are building a software engineering culture, you should write as many of your own tools as you can get away with. Nothing builds culture like a shared unique experience.
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#70Creator of "Jira Clone" here. First of all I want to make it clear that this is just a showcase/demo product. It's definitely not something I'm planning to sell. Additionally, it's not even remotely production ready, and it's missing about a zillion features that would make it a full-fledged project management software. The main reason I built this was to have a good showcase for potential future clients. The second…
For technology showcases the RealWorld example is pretty popular: https://github.com/gothinkster/realworld. Showcasing your tech prowess is quite a bit different, I get that.
Kudos for readable hook-based code. :)